Like gh and tea, but aspiring to be compatible with multiple forge types to avoid using different tools for each.

Find a file

Marc Cataford 9a6b33c4d7 All checks were successful / tests (pull_request) Successful in 44s Details / static-analysis (pull_request) Successful in 1m25s Details / export-trace (pull_request) Successful in 31s Details ci: run pre-commit steps as CI checks		2024-11-02 18:32:25 -04:00
.forgejo/workflows	ci: run pre-commit steps as CI checks	2024-11-02 18:32:25 -04:00
frg	build: add pre-commit, hook set, ensure checks pass	2024-11-02 18:30:39 -04:00
tests	build: add pre-commit, hook set, ensure checks pass	2024-11-02 18:30:39 -04:00
.gitignore	Initial commit	2024-11-02 18:44:49 +00:00
.pre-commit-config.yaml	build: add pre-commit, hook set, ensure checks pass	2024-11-02 18:30:39 -04:00
.python-version	feat: initial push	2024-11-02 15:00:48 -04:00
bootstrap.sh	build: add pre-commit, hook set, ensure checks pass	2024-11-02 18:30:39 -04:00
LICENSE	Initial commit	2024-11-02 18:44:49 +00:00
pyproject.toml	build: add pre-commit, hook set, ensure checks pass	2024-11-02 18:30:39 -04:00
README.md	docs: add readme stub	2024-11-02 15:19:37 -04:00
uv.lock	build: add pre-commit, hook set, ensure checks pass	2024-11-02 18:30:39 -04:00

README.md

forge-tools

Like gh and tea, but aspiring to be compatible with multiple forge types to avoid using different tools for each.

Usage

frg --help will give you an overview of what's available!

Development

This uses uv to manage dependencies; make sure it's installed before proceeding.

Direction

The primary intention of this is to make a more hackable version of gh-like tooling for my own purposes. This is not aiming feature parity or production-level quality.