|
8 | 8 | [](https://github.com/Bharath-code/git-scope/stargazers) |
9 | 9 | [](https://buymeacoffee.com/iam_pbk) |
10 | 10 |
|
| 11 | +🌐 **Website:** [bharath-code.github.io/git-scope](https://bharath-code.github.io/git-scope/) |
| 12 | + |
11 | 13 |  |
12 | 14 |
|
13 | 15 | --- |
14 | 16 |
|
| 17 | +## 🛡️ Trust & Safety |
| 18 | + |
| 19 | +git-scope is designed to be safe to run frequently and safe to recommend. |
| 20 | + |
| 21 | +- **Read-only by design** — it does not modify repositories |
| 22 | +- **Local-first** — no network access, no telemetry, no accounts |
| 23 | +- **Predictable** — no background services or daemons |
| 24 | +- **Conservative scope** — focused on visibility, not automation |
| 25 | + |
| 26 | +These choices make git-scope suitable for daily use and work environments where reliability and transparency matter. |
| 27 | + |
| 28 | +--- |
| 29 | + |
15 | 30 | ## ⚡ Installation |
16 | 31 |
|
17 | 32 | Get started in seconds. |
@@ -94,6 +109,25 @@ git-scope -h # Show help |
94 | 109 |
|
95 | 110 | ----- |
96 | 111 |
|
| 112 | +## 🎯 Use Cases |
| 113 | + |
| 114 | +git-scope excels in environments where multi-repo complexity is a daily burden: |
| 115 | + |
| 116 | +* **Microservices Management** — Quickly verify if all your services are on the correct branch and have no unpushed changes. |
| 117 | +* **OSS Contribution Tracking** — Keep tabs on various upstream forks and personal branches in one view. |
| 118 | +* **Infrastructure as Code (IaC)** — Monitor multiple Terraform/CloudFormation repos for configuration drift or uncommitted edits. |
| 119 | +* **Context Recovery** — Instantly see where you left off after a weekend or a holiday without running `git status` 20 times. |
| 120 | + |
| 121 | +----- |
| 122 | + |
| 123 | +## 🏆 The git-scope Advantage |
| 124 | + |
| 125 | +While many Git tools focus on the *micro* (committing, staging, diffing), git-scope is built for the *macro*. |
| 126 | + |
| 127 | +Typical git workflows involve "tunnel vision"—working deep inside one repository. git-scope provides the "command center" view. It is intentionally **read-only**, **local-first**, and **blazing fast** (<10ms), making it the perfect companion to tools like `lazygit`, `gitui`, or VS Code. |
| 128 | + |
| 129 | +----- |
| 130 | + |
97 | 131 | ## ⌨️ Keyboard Shortcuts |
98 | 132 |
|
99 | 133 | | Key | Action | |
@@ -156,11 +190,43 @@ I built `git-scope` to solve the **"Multi-Repo Blindness"** problem. It gives me |
156 | 190 |
|
157 | 191 | - [x] In-app workspace switching with Tab completion |
158 | 192 | - [x] Symlink resolution for devcontainers/Codespaces |
159 | | - - [ ] Background file watcher (real-time updates) |
| 193 | + - [x] Background file watcher (real-time updates) |
160 | 194 | - [ ] Quick actions (bulk pull/fetch) |
161 | 195 | - [ ] Repo grouping (Service / Team / Stack) |
162 | 196 | - [ ] Custom team dashboards |
163 | 197 |
|
| 198 | +## ❓ FAQ |
| 199 | + |
| 200 | +### How do you manage multiple Git repositories locally? |
| 201 | + |
| 202 | +git-scope provides a fast, read-only terminal dashboard that shows the status of many local Git repositories at once. It helps developers regain context across projects without switching directories or running commands repeatedly. |
| 203 | + |
| 204 | +### What problem does git-scope solve? |
| 205 | + |
| 206 | +git-scope reduces context switching when working across many Git repositories, such as microservices, tools, or configuration repos. It gives a single overview of repository state so developers can quickly see what needs attention. |
| 207 | + |
| 208 | +### Is git-scope safe to use at work? |
| 209 | + |
| 210 | +Yes. git-scope is read-only by design, runs entirely locally, has no network access or telemetry, and does not modify repositories. This makes it safe for daily and work use. |
| 211 | + |
| 212 | +### Does git-scope replace git commands? |
| 213 | + |
| 214 | +No. git-scope does not perform git actions like commit, push, or pull. It focuses on visibility and orientation, not automation. |
| 215 | + |
| 216 | +### Is git-scope suitable for monorepos? |
| 217 | + |
| 218 | +git-scope is designed for multi-repo (polyrepo) workflows. It is not intended to manage monorepos. |
| 219 | + |
| 220 | +### What platforms does git-scope support? |
| 221 | + |
| 222 | +git-scope runs on macOS, Linux, and Windows. |
| 223 | + |
| 224 | +### How is git-scope different from other git TUIs? |
| 225 | + |
| 226 | +Most git TUIs focus on interacting with a single repository. git-scope focuses on visibility across many repositories and stays intentionally read-only. |
| 227 | + |
| 228 | +--- |
| 229 | + |
164 | 230 | ## 📄 License |
165 | 231 |
|
166 | 232 | MIT © [Bharath-code](https://github.com/Bharath-code) |
|
0 commit comments