A Python desktop application that brings everyday Git work, advanced repository engineering, GitHub workflows, recovery, release tooling, and developer utilities into one user-friendly command center.
GitHub Command Center helps developers and repository maintainers complete common and advanced Git tasks without memorizing every command. It combines a streamlined Local Git workspace with specialist tools available through grouped navigation and the Ctrl+K command palette.
- Review working-tree changes, stage files or hunks, write commits, and inspect diffs.
- Browse commit history, compare refs, inspect objects, search revisions, and visualize the commit graph.
- Create, rename, compare, clean up, and safely delete branches and tags.
- Fetch, pull, push, prune, inspect remotes, and diagnose upstream configuration.
- Manage stashes and worktrees, including stash diff and conflict previews.
- Run interactive rebase, cherry-pick queues, bisect workflows, revert queues, and merge previews.
- Recover through reflog, dangling-object, detached-HEAD, lost-and-found, and reset recovery tools.
- Work with GitHub pull requests, Actions, releases, security workflows, and repository readiness checks.
- Use developer tooling for code search, patch series, quality checks, build validation, Git objects, and revision explanation.
- Create release evidence, checksums, manifests, SBOM-ready outputs, and deterministic archives.
Workspace Profiles now include:
- Real-time filtering by profile name, repository path, branch, or note.
- A Check health action for one selected profile or all visible profiles.
- Statuses for
Ready,Missing,Not a Git repository, andBranch missing. - Read-only repository checks that do not change the working tree.
The v3.81 Workspace Profiles feature remains available for saving a friendly name, repository, preferred branch, and note, and for importing or exporting profiles as JSON.
- Python 3.10 or newer.
- Git installed and available on
PATH. - Tkinter, normally included with standard Windows Python installations.
- A GitHub CLI or GitHub authentication setup only for features that interact with GitHub.
On Debian or Ubuntu:
sudo apt update
sudo apt install python3-tk gitOn Fedora:
sudo dnf install python3-tkinter git- Download
github_command_center_python_v3.82.0.zip. - Verify its SHA-256 checksum against
github_command_center_python_v3.82.0.sha256. - Extract the archive.
- Open a terminal in the extracted folder.
- Start the app:
python app.pyWindows users can also run:
run_windows.batLinux users can run:
chmod +x run_linux.sh
./run_linux.shpython -m pip install .
github-command-centerFor contributors and validation tooling:
python -m pip install -e ".[dev]"- Start the application.
- Select Choose Repository and open an existing Git repository.
- Use the daily-action toolbar for refresh, fetch, pull, push, commit, history, branches, stash, and worktrees.
- Press
Ctrl+Kto open the complete specialist-tool catalog. - Select Workspaces to save or reopen frequently used repository and branch contexts.
The interface groups work into nine areas:
- Changes
- History
- Branches
- Sync
- Review
- GitHub
- Release
- Recover
- Advanced
The goal is to keep daily actions visible while keeping specialist tools discoverable without overcrowding the main screen.
- Select Workspaces in the Local Git header.
- Choose Save current to store the current repository and branch.
- Add an optional note such as
release workspaceorcustomer hotfix. - Use the filter box to narrow profiles.
- Select a profile and choose Check health, or clear the selection to check all visible profiles.
- Double-click a profile or choose Open to open the repository and switch to its preferred branch.
- Use Export and Import to back up or move profiles.
Profiles are stored at:
~/.github_command_center/workspace_profiles.json
| Shortcut | Action |
|---|---|
Ctrl+K |
Open command palette |
F5 |
Refresh repository |
Ctrl+Enter |
Commit |
Tab / Shift+Tab |
Move keyboard focus |
Enter / Space |
Activate the focused control |
- No
shell=Truecommand execution. - Feature domains cannot invoke subprocesses directly and must use the process gateway.
- Zero bare exception handlers and zero direct broad
except Exceptionhandlers. - Destructive operations use confirmations, previews, policies, or recovery guidance where appropriate.
- Plugin trust and plugin-security checks are included.
- CI includes Ruff, Bandit, pip-audit, CodeQL, dependency review, test, architecture, coverage, and packaging gates.
- Release archives include deterministic packaging, SHA-256 checksums, file manifests, and integrity validation.
The application uses a focused UI shell, bounded feature domains, compatibility facades, services, and centralized command/process gateways.
UI shell
-> centers and bounded feature domains
-> services and policy boundaries
-> Git command gateway / process gateway / GitHub integrations
Architecture limits are enforced automatically for shell size, domain size, class count, facade size, subprocess boundaries, and unsafe shell execution.
See ARCHITECTURE.md for details.
User preferences and Workspace Profiles are stored under:
~/.github_command_center/
The application does not store repository contents in this folder. Export important workspace profiles before replacing or resetting your user configuration.
Confirm:
git --versionIf this fails, install Git and restart the terminal or application.
On Linux, install the platform Tkinter package. On Windows, rerun the official Python installer and enable Tcl/Tk support.
Open Workspaces, select the profile, and run Check health. If the folder moved, delete the old profile and save the repository again from its new path.
The repository still opens, but the app shows a warning. Verify that the branch exists locally, fetch the repository, or update the saved profile.
Verify network access and the relevant GitHub authentication or GitHub CLI setup. Local Git functionality remains available independently.
Run the standard local validation:
python -m compileall -q .
python -m pytest -q
python scripts/architecture_gate.py
python scripts/security_gate.py
python scripts/release_readiness_gate.py
python scripts/packaging_gate.pyCI additionally runs supported Python/OS matrices, coverage, Ruff, Bandit, pip-audit, CodeQL, dependency review, package build, clean installation, SBOM generation, and artifact attestation.
git clone <repository-url>
cd <repository-folder>
python -m venv .venvActivate the environment and install development dependencies:
python -m pip install -e ".[dev]"
python -m pytest -qWhen adding a feature:
- Keep UI code in a center or bounded feature domain.
- Put reusable logic in a service.
- Route Git and external commands through the approved gateways.
- Add tests and update README, changelog, release notes, and user guidance.
- Run every release gate before packaging.
USER_GUIDE.md: user workflows and operating guidance.ARCHITECTURE.md: application structure and boundaries.SECURITY.md: vulnerability reporting and security practices.ACCESSIBILITY.md: keyboard and accessibility design rules.CONTRIBUTING.md: contributor expectations.CHANGELOG.md: cumulative release history.RELEASE_NOTES.md: current release details.ROADMAP.md: planned product direction.PLUGIN_SECURITY.md: plugin trust and validation controls.WINDOWS_VALIDATION.md: Windows-specific validation.
Contributions should include tests, documentation updates, and successful architecture, security, readiness, and packaging gates. See CONTRIBUTING.md for the complete process.
Do not disclose suspected vulnerabilities publicly before maintainers can assess them. Follow the process in SECURITY.md.
No license file is currently included in this release. Before public redistribution or external contributions, the project owner should add an explicit license such as MIT, Apache-2.0, or the organization-approved proprietary license.
Current version: 3.82.0
Artifact: github_command_center_python_v3.82.0.zip
- v3.71.0 added Ref Compare, Revision Explain, Git log visualization, stash workbench, and worktree workbench capabilities.
- v3.72.0 added interactive commit graph filters plus stash diff and conflict previews.
- Later releases retained these features while improving architecture, error handling, CI/security, packaging, release evidence, process boundaries, and Workspace Profiles.