gwitch 0.1.0__tar.gz

gwitch-0.1.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,17 @@
+---
+name: Bug report
+about: Something isn't working as expected
+labels: bug
+---
+
+**What command did you run?**
+
+**What did you expect to happen?**
+
+**What actually happened?** (include the full output)
+
+**Environment**
+- `gw` version (`pipx list` or `pip show gw`):
+- OS:
+- Shell (zsh/bash/fish):
+- `gh --version` (if relevant):

gwitch-0.1.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,11 @@
+---
+name: Feature request
+about: Suggest an idea for gw
+labels: enhancement
+---
+
+**What problem does this solve?**
+
+**What would you like `gw` to do instead?**
+
+**Anything else?** (alternatives considered, related issues, etc.)

gwitch-0.1.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,8 @@
+## What does this change?
+
+## Why?
+
+## Testing
+
+- [ ] `python -m pytest -v` passes locally
+- [ ] Added/updated tests for this change

gwitch-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,34 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Configure git identity for tests
+        run: |
+          git config --global user.name "CI"
+          git config --global user.email "ci@example.com"
+          git config --global init.defaultBranch main
+
+      - name: Install gw
+        run: pip install -e ".[dev]"
+
+      - name: Run tests
+        run: python -m pytest -v

gwitch-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,40 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Build package
+        run: |
+          pip install build
+          python -m build
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

gwitch-0.1.0/.gitignore

@@ -0,0 +1,10 @@
+.worktrees/
+.superpowers/
+.venv/
+__pycache__/
+*.pyc
+*.egg-info/
+dist/
+build/
+.pytest_cache/
+docs/plans/

gwitch-0.1.0/CHANGELOG.md

@@ -0,0 +1,36 @@
+# Changelog
+
+All notable changes to this project are documented here.
+Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+
+## [Unreleased]
+
+### Added
+
+- `gw init <shell> --install` — for `zsh`/`bash`, write the `gw-prompt`
+  script to `~/.local/bin/gw-prompt` and append an idempotent, marked block
+  to your shell rc file automatically, instead of pasting the snippet by hand.
+- Remote-account mismatch check: `gw use <name>` now records this repo's
+  remote-to-account mapping in global git config, and `gw init <shell>
+  --install` additionally installs a `gw-check` script wired to run on every
+  shell `cd`, warning (to stderr, non-blocking) when the account active in
+  the repo you land in doesn't match the account last recorded for its
+  remote.
+
+## [0.1.0] - 2026-08-29
+
+Initial release.
+
+### Added
+
+- `gw account add/list/remove` — register, list, and remove git/GitHub
+  accounts, with optional SSH key generation.
+- `gw use <name>` — activate an account for the current repo: local (never
+  global) `user.name`/`user.email`/`core.sshCommand`, plus a best-effort
+  `gh auth switch`. Warns when run inside a linked git worktree, since git
+  shares local config across worktrees by default.
+- `gw status` / `gw whoami` — show the active account for the current repo,
+  and flag drift between it and `gh`'s currently active account.
+- `gw init zsh|bash|fish` — print a pure-shell prompt snippet (no Python
+  spawned per render) showing the active account.
+- `pipx install .` packaging with a `gw` console script.

gwitch-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,63 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in
+our community a harassment-free experience for everyone, regardless of age,
+body size, visible or invisible disability, ethnicity, sex characteristics,
+gender identity and expression, level of experience, education,
+socio-economic status, nationality, personal appearance, race, religion, or
+sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open,
+welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political
+  attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing our
+standards of acceptable behavior and will take appropriate and fair
+corrective action in response to any behavior that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces (issues, pull
+requests, discussions) and when an individual is officially representing
+the project in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the maintainers at **askmaurya48@gmail.com**. All complaints
+will be reviewed and investigated promptly and fairly.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html

gwitch-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,45 @@
+# Contributing to gw
+
+Thanks for considering a contribution.
+
+## Development setup
+
+```bash
+git clone https://github.com/isamrish/gwitch.git
+cd gwitch
+python3 -m venv .venv
+.venv/bin/pip install -e ".[dev]"
+```
+
+## Running tests
+
+```bash
+.venv/bin/python -m pytest -v
+```
+
+Tests exercise real `git`, `ssh-keygen`, and (mocked) `gh` subprocess calls
+against temporary directories — no network access or existing GitHub
+account is required to run the suite.
+
+## Making a change
+
+1. Open an issue first for anything beyond a small fix, so we can agree on
+   the approach before you put work into it.
+2. Follow the existing code style: qualified module imports
+   (`from gw import config`, not `from gw.config import x`) so tests can
+   monkeypatch cleanly — this convention is used throughout the codebase.
+3. Add or update tests for any behavior change. Real git/ssh-keygen calls
+   are preferred over mocks where practical; `gh` calls are mocked since
+   they need live auth.
+4. Run the full test suite before opening a pull request.
+
+## Pull requests
+
+Keep PRs focused — one change per PR is easier to review than a bundle of
+unrelated fixes. Describe what changed and why in the PR description.
+
+## Reporting bugs
+
+Open a GitHub issue with the command you ran, what you expected, and what
+happened instead. For anything involving SSH keys, GitHub tokens, or other
+credentials, see [SECURITY.md](SECURITY.md) instead of a public issue.

gwitch-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Amrish Kushwaha
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

gwitch-0.1.0/PKG-INFO

@@ -0,0 +1,143 @@
+Metadata-Version: 2.5
+Name: gwitch
+Version: 0.1.0
+Summary: Switch between git/GitHub accounts per repository.
+Project-URL: Homepage, https://github.com/isamrish/gwitch
+Project-URL: Repository, https://github.com/isamrish/gwitch
+Project-URL: Issues, https://github.com/isamrish/gwitch/issues
+Author-email: Amrish Kushwaha <askmaurya48@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Version Control :: Git
+Classifier: Topic :: Utilities
+Requires-Python: >=3.9
+Requires-Dist: toml>=0.10
+Requires-Dist: typer>=0.9
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# gw
+
+[![CI](https://github.com/isamrish/gwitch/actions/workflows/ci.yml/badge.svg)](https://github.com/isamrish/gwitch/actions/workflows/ci.yml)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
+
+Switch between multiple git/GitHub accounts, per repository, and see which
+account is active right in your shell prompt.
+
+## Install
+
+    pipx install gwitch
+
+Published on PyPI as `gwitch`; installs the `gw` command. Or, from a
+checkout of this repository:
+
+    pipx install .
+
+## Quick start
+
+    gw account add personal
+    gw account add work
+
+    cd ~/code/some-repo
+    gw use personal
+    gw status
+
+## Shell prompt
+
+    gw init zsh    # or bash / fish
+
+prints a small shell function, plus a one-line instruction for wiring it
+into your prompt — paste both into your shell config yourself. `gw` never
+edits your shell rc files automatically.
+
+    gw init zsh --install    # or bash
+
+`--install` does the wiring for you, for `zsh`/`bash` only (not `fish`
+yet): it writes a `gw-prompt` script to `~/.local/bin/gw-prompt` and a
+`gw-check` script to `~/.local/bin/gw-check` (the cd-triggered account-check
+described below), and appends two marked blocks to your rc file — one per
+script. It's idempotent — safe to re-run. Note for macOS bash users:
+`~/.bashrc` isn't read by login shells (Terminal and iTerm start bash as a
+login shell), so unless you've already wired `~/.bashrc` to be sourced from
+`~/.bash_profile`, you'll need to add that yourself for the installed
+integration to take effect.
+
+## What `gw use <account>` changes
+
+- `user.name` / `user.email` — local to the current repo only (`git config --local`)
+- `core.sshCommand` — forces the SSH key registered for that account
+- `gw.account` — a marker read by `gw status` and the shell prompt function
+- `gw-remote-map.<remote URL>.account` — records this repo's remote in **global** git config, for the cd-triggered mismatch check below
+
+`gw use` also records this repo's remote-to-account mapping in **global**
+git config (for the cd-triggered mismatch check, see below) — everything
+else stays local-only. None of this touches `~/.ssh/config` or ssh-agent.
+
+## Remote-account mismatch check
+
+With `gw init <shell> --install`, a `gw-check` script is wired to run every
+time your shell `cd`s into a different directory. If the repo you land in
+has an `origin` remote that `gw use <account>` has previously recorded, and
+the account currently active in that repo doesn't match, it prints a
+warning to stderr telling you which account to switch to. It never blocks
+or changes anything — it's purely informational.
+
+## Known limitations
+
+**`gh` (GitHub CLI) authentication is global, not per-repo.** GitHub CLI's
+authenticated account is global to your machine (`gh` keeps one active user
+per host), not per-repo — that's inherent to how `gh` itself works. `gw use
+<account>` will call `gh auth switch` for you, which changes `gh`'s active
+account machine-wide, even for other repos/terminal tabs, until you `gw use`
+a different account somewhere else. Your git identity and SSH key stay
+correctly isolated per-repo regardless.
+
+`gw status` shows both this repo's git identity and gh's currently active
+account as separate lines, so if they've drifted apart it's visible rather
+than silent.
+
+**Linked git worktrees share git identity.** `git config --local` in a
+linked worktree (created via `git worktree add`) resolves to the *same*
+shared config file as the main checkout — git only isolates local config
+per-worktree if the repo opts into `extensions.worktreeConfig`, which `gw`
+does not assume. That means `gw use <account>` run inside a linked worktree
+changes the identity for the main checkout and every sibling worktree of
+that repo too, not just the worktree you ran it in. `gw use` detects this
+and prints a warning when you run it inside a linked worktree, but it does
+not block the switch or set up per-worktree config automatically.
+
+**The remote-account check is last-write-wins, URL-exact, and cd-triggered
+only.** The `gw-remote-map` registry has no per-clone tracking: running `gw
+use <account>` anywhere for a given remote overwrites what "the right
+account" means for every other clone of that remote — this is intentional,
+not a bug. It also matches on the exact remote URL string, so an SSH clone
+and an HTTPS clone of the same repo are treated as two unrelated remotes.
+And because the check only runs on `cd`, a shell already sitting in a
+mismatched repo when it starts won't warn until you `cd` away and back.
+
+## Commands
+
+- `gw account add <name>` — register an account (prompts for git name/email,
+  GitHub username; can generate a new SSH key for you)
+- `gw account list` — list registered accounts
+- `gw account remove <name>` — remove a registered account
+- `gw use <name>` — activate an account for the current repo
+- `gw status` / `gw whoami` — show the active account for the current repo
+- `gw init <shell>` — print the shell prompt snippet for `zsh`, `bash`, or
+  `fish`; add `--install` (`zsh`/`bash` only) to write and wire it up automatically
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for dev setup and how to run the
+tests. Please follow the [Code of Conduct](CODE_OF_CONDUCT.md). For security
+issues, see [SECURITY.md](SECURITY.md) instead of opening a public issue.
+
+## License
+
+[MIT](LICENSE)

gwitch-0.1.0/README.md

@@ -0,0 +1,119 @@
+# gw
+
+[![CI](https://github.com/isamrish/gwitch/actions/workflows/ci.yml/badge.svg)](https://github.com/isamrish/gwitch/actions/workflows/ci.yml)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
+
+Switch between multiple git/GitHub accounts, per repository, and see which
+account is active right in your shell prompt.
+
+## Install
+
+    pipx install gwitch
+
+Published on PyPI as `gwitch`; installs the `gw` command. Or, from a
+checkout of this repository:
+
+    pipx install .
+
+## Quick start
+
+    gw account add personal
+    gw account add work
+
+    cd ~/code/some-repo
+    gw use personal
+    gw status
+
+## Shell prompt
+
+    gw init zsh    # or bash / fish
+
+prints a small shell function, plus a one-line instruction for wiring it
+into your prompt — paste both into your shell config yourself. `gw` never
+edits your shell rc files automatically.
+
+    gw init zsh --install    # or bash
+
+`--install` does the wiring for you, for `zsh`/`bash` only (not `fish`
+yet): it writes a `gw-prompt` script to `~/.local/bin/gw-prompt` and a
+`gw-check` script to `~/.local/bin/gw-check` (the cd-triggered account-check
+described below), and appends two marked blocks to your rc file — one per
+script. It's idempotent — safe to re-run. Note for macOS bash users:
+`~/.bashrc` isn't read by login shells (Terminal and iTerm start bash as a
+login shell), so unless you've already wired `~/.bashrc` to be sourced from
+`~/.bash_profile`, you'll need to add that yourself for the installed
+integration to take effect.
+
+## What `gw use <account>` changes
+
+- `user.name` / `user.email` — local to the current repo only (`git config --local`)
+- `core.sshCommand` — forces the SSH key registered for that account
+- `gw.account` — a marker read by `gw status` and the shell prompt function
+- `gw-remote-map.<remote URL>.account` — records this repo's remote in **global** git config, for the cd-triggered mismatch check below
+
+`gw use` also records this repo's remote-to-account mapping in **global**
+git config (for the cd-triggered mismatch check, see below) — everything
+else stays local-only. None of this touches `~/.ssh/config` or ssh-agent.
+
+## Remote-account mismatch check
+
+With `gw init <shell> --install`, a `gw-check` script is wired to run every
+time your shell `cd`s into a different directory. If the repo you land in
+has an `origin` remote that `gw use <account>` has previously recorded, and
+the account currently active in that repo doesn't match, it prints a
+warning to stderr telling you which account to switch to. It never blocks
+or changes anything — it's purely informational.
+
+## Known limitations
+
+**`gh` (GitHub CLI) authentication is global, not per-repo.** GitHub CLI's
+authenticated account is global to your machine (`gh` keeps one active user
+per host), not per-repo — that's inherent to how `gh` itself works. `gw use
+<account>` will call `gh auth switch` for you, which changes `gh`'s active
+account machine-wide, even for other repos/terminal tabs, until you `gw use`
+a different account somewhere else. Your git identity and SSH key stay
+correctly isolated per-repo regardless.
+
+`gw status` shows both this repo's git identity and gh's currently active
+account as separate lines, so if they've drifted apart it's visible rather
+than silent.
+
+**Linked git worktrees share git identity.** `git config --local` in a
+linked worktree (created via `git worktree add`) resolves to the *same*
+shared config file as the main checkout — git only isolates local config
+per-worktree if the repo opts into `extensions.worktreeConfig`, which `gw`
+does not assume. That means `gw use <account>` run inside a linked worktree
+changes the identity for the main checkout and every sibling worktree of
+that repo too, not just the worktree you ran it in. `gw use` detects this
+and prints a warning when you run it inside a linked worktree, but it does
+not block the switch or set up per-worktree config automatically.
+
+**The remote-account check is last-write-wins, URL-exact, and cd-triggered
+only.** The `gw-remote-map` registry has no per-clone tracking: running `gw
+use <account>` anywhere for a given remote overwrites what "the right
+account" means for every other clone of that remote — this is intentional,
+not a bug. It also matches on the exact remote URL string, so an SSH clone
+and an HTTPS clone of the same repo are treated as two unrelated remotes.
+And because the check only runs on `cd`, a shell already sitting in a
+mismatched repo when it starts won't warn until you `cd` away and back.
+
+## Commands
+
+- `gw account add <name>` — register an account (prompts for git name/email,
+  GitHub username; can generate a new SSH key for you)
+- `gw account list` — list registered accounts
+- `gw account remove <name>` — remove a registered account
+- `gw use <name>` — activate an account for the current repo
+- `gw status` / `gw whoami` — show the active account for the current repo
+- `gw init <shell>` — print the shell prompt snippet for `zsh`, `bash`, or
+  `fish`; add `--install` (`zsh`/`bash` only) to write and wire it up automatically
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for dev setup and how to run the
+tests. Please follow the [Code of Conduct](CODE_OF_CONDUCT.md). For security
+issues, see [SECURITY.md](SECURITY.md) instead of opening a public issue.
+
+## License
+
+[MIT](LICENSE)

gwitch-0.1.0/SECURITY.md

@@ -0,0 +1,25 @@
+# Security Policy
+
+`gw` manages SSH keys and delegates to GitHub CLI's stored authentication
+tokens. If you find a security issue — anything that could leak, misuse, or
+mismanage a credential — please report it privately rather than opening a
+public issue.
+
+## Reporting a vulnerability
+
+Email **askmaurya48@gmail.com** with:
+
+- A description of the issue and its potential impact
+- Steps to reproduce, if possible
+- Any relevant version/environment details
+
+Please do not open a public GitHub issue for security reports until the
+issue has been addressed.
+
+## Scope
+
+`gw` never stores secrets itself — SSH keys are referenced by path only,
+and GitHub tokens are fetched from `gh`'s own storage on demand, never
+persisted by `gw`. Reports about `gw` reading, storing, or transmitting a
+credential in a way that isn't documented in the README's "Known
+limitations" section are especially welcome.