README
¶
_ _ _ _ _
| |__ (_) |_ __ _(_) |_
| '_ \| | __/ _` | | __|
| |_) | | || (_| | | |_
|_.__/|_|\__\__, |_|\__|
|___/
git + Bitbucket Data Center CLI with a hook-based plugin system.
Status: pre-alpha. Under active development. The CLI surface and plugin protocol are in place. Verbs (
pr,commit,push,branch,doctor) are stubs — implementation is in flight. Watch the repo for v0.1.0.
What
bitgit is a generic-verb git CLI (bitgit pr create, bitgit pr show <id>,
bitgit commit, bitgit push, bitgit doctor, …) that wraps git and
Bitbucket Data Center — and lets you inject veto/mutate logic via plugins.
Plugins:
- Auto-attach based on git remote, project key, repo slug, or branch prefix.
- Speak JSON-RPC 2.0 over stdio — write them in any language.
- Hook into
pre-pr-create,post-pr-create,pre-pr-merge,pre-commit,pre-push, … - Can veto an operation (e.g. corp policy: "no force-push to release/*") or mutate it (e.g. "auto-prepend Jira key to PR title").
Designed for shops where every team has its own conventions and you want one CLI that respects all of them without forking.
Why
gh and tea don't speak Bitbucket DC. hub is unmaintained.
None of them let you wedge in language-agnostic policy plugins.
Install
Pre-alpha; install methods become stable at v0.1.0.
# Once stable releases exist:
brew install exisz/tap/bitgit
# Always works from source:
go install github.com/exisz/bitgit/cmd/bitgit@latest
# Pre-built binaries (per release):
# https://github.com/exisz/bitgit/releases
Quick start
bitgit --help
bitgit doctor # sanity-check chassis + plugins
bitgit plugin list # installed plugins under ~/.bitgit/plugins/
bitgit pr create # (stub — under development)
Plugins
Plugins live under ~/.bitgit/plugins/<name>/ with a plugin.toml manifest.
Read docs/plugin-protocol.md for the full wire
spec. A reference plugin in Go ships in plugins/example-github/.
Minimal plugin manifest:
name = "corp-policy"
version = "1.0.0"
entrypoint = "./corp-policy"
hooks = ["pre-pr-create", "pre-pr-merge"]
[match]
remote_host = ["bitbucket.example.com"]
project_key = ["PLAT"]
A plugin is just any executable that reads JSON-RPC requests on stdin and writes JSON-RPC responses on stdout. ~50 lines in any language.
Architecture
| Layer | Repo | Purpose |
|---|---|---|
| Public chassis | exisz/bitgit (this repo) |
CLI surface, plugin runtime, docs |
| Private overlay | exisz/bitgit-workspace |
Shop-specific verb implementations + plugins (private) |
| User config | ~/.bitgit/ |
config.toml, plugins/, secrets/, cache/ |
The chassis works standalone. The private overlay is optional and never imported by the chassis.
Repo layout
cmd/bitgit/ CLI entrypoint
internal/cli/ cobra command tree + verb stubs
internal/plugin/ discovery, match-rule, JSON-RPC stdio, hook dispatcher
plugins/ in-repo reference plugins
docs/ landing page (index.html), plugin-protocol.md, config.md
.github/workflows/ ci.yml (PR gate) + release.yml (tag → goreleaser)
.goreleaser.yml cross-platform binaries + Homebrew tap
Contributing
See CONTRIBUTING.md. The empire's Go OSS standard lives at
~/.openclaw/skills/empire-standard/references/go-oss-standard.md for
internal contributors; external contributors only need to follow the
guidelines in CONTRIBUTING.
License
MIT © Exis. See LICENSE.
Directories
¶
| Path | Synopsis |
|---|---|
|
cmd
|
|
|
bitgit
command
Command bitgit is a git+Bitbucket Data Center CLI with a hook-based plugin system.
|
Command bitgit is a git+Bitbucket Data Center CLI with a hook-based plugin system. |
|
internal
|
|
|
cli
Package cli wires the cobra command tree.
|
Package cli wires the cobra command tree. |
|
plugin
Package plugin owns the bitgit plugin protocol: discovery on disk, match-rule evaluation, JSON-RPC stdio transport, and hook dispatch.
|
Package plugin owns the bitgit plugin protocol: discovery on disk, match-rule evaluation, JSON-RPC stdio transport, and hook dispatch. |
|
plugins
|
|
|
example-github
command
Command example-github is a reference plugin for bitgit.
|
Command example-github is a reference plugin for bitgit. |