gitstow 0.7.2__tar.gz → 0.9.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- gitstow-0.9.0/.mailmap +1 -0
- gitstow-0.9.0/BACKLOG.md +54 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/CHANGELOG.md +42 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/CONTRIBUTING.md +8 -0
- gitstow-0.9.0/LICENSE +232 -0
- gitstow-0.9.0/NOTICE +36 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/PKG-INFO +21 -6
- {gitstow-0.7.2 → gitstow-0.9.0}/README.md +14 -2
- {gitstow-0.7.2 → gitstow-0.9.0}/design_handoff_gitstow_landing/Gitstow Landing.dc.html +2 -2
- {gitstow-0.7.2 → gitstow-0.9.0}/design_handoff_gitstow_landing/README.md +2 -2
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/building/implementation-plan.md +1 -1
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/user/commands.md +38 -10
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/user/concepts.md +3 -1
- {gitstow-0.7.2 → gitstow-0.9.0}/pyproject.toml +10 -5
- {gitstow-0.7.2 → gitstow-0.9.0}/scripts/release.sh +3 -0
- gitstow-0.9.0/site/LICENSE.txt +232 -0
- gitstow-0.9.0/site/NOTICE.txt +20 -0
- gitstow-0.9.0/site/assets/fonts/OFL-bricolage-grotesque.txt +93 -0
- gitstow-0.9.0/site/assets/fonts/OFL-jetbrains-mono.txt +93 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/site/index.html +4 -2
- {gitstow-0.7.2 → gitstow-0.9.0}/site/style.css +5 -0
- gitstow-0.9.0/src/gitstow/__init__.py +6 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/__main__.py +3 -0
- gitstow-0.9.0/src/gitstow/cli/__init__.py +4 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/add.py +86 -61
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/config_cmd.py +9 -1
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/diff_cmd.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/doctor.py +21 -1
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/exec_cmd.py +5 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/export_cmd.py +77 -54
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/fetch.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/helpers.py +14 -2
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/list_cmd.py +8 -4
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/main.py +3 -1
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/manage.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/migrate.py +13 -9
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/onboard.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/open_cmd.py +9 -4
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/pull.py +36 -8
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/remove.py +10 -10
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/search.py +5 -71
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/serve.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/setup_ai.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/shell.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/skill_cmd.py +14 -14
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/stats.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/status.py +7 -1
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/update.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/cli/workspace_cmd.py +12 -1
- gitstow-0.9.0/src/gitstow/core/__init__.py +4 -0
- gitstow-0.9.0/src/gitstow/core/collection_io.py +206 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/core/config.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/core/diff.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/core/discovery.py +19 -5
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/core/git.py +242 -13
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/core/locking.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/core/operations.py +7 -10
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/core/parallel.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/core/paths.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/core/repo.py +78 -5
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/core/status_model.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/core/tailscale.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/core/url_parser.py +85 -13
- gitstow-0.9.0/src/gitstow/mcp/__init__.py +4 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/mcp/server.py +36 -41
- gitstow-0.9.0/src/gitstow/skill/LICENSE +232 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/skill/SKILL.md +9 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/__init__.py +3 -0
- gitstow-0.9.0/src/gitstow/web/routes/__init__.py +4 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/routes/collection.py +55 -51
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/routes/dashboard.py +22 -2
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/routes/pages.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/routes/repos.py +32 -31
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/routes/system.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/routes/workspaces.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/server.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/static/app.css +19 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/static/dashboard.js +5 -0
- gitstow-0.9.0/src/gitstow/web/static/fonts/OFL-bricolage-grotesque.txt +93 -0
- gitstow-0.9.0/src/gitstow/web/static/fonts/OFL-jetbrains-mono.txt +93 -0
- gitstow-0.9.0/src/gitstow/web/static/vendor/LICENSE-htmx.txt +25 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/static/vendor/VENDORED.md +4 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/templates/_repo_drawer.html +2 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/templates/add_repo.html +2 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/templates/base.html +2 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/templates/dashboard.html +9 -1
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/templates/partials/changes_section.html +2 -0
- gitstow-0.9.0/src/gitstow/web/templates/partials/dashboard_rows.html +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/templates/partials/diff_view.html +2 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/templates/partials/fetch_summary.html +2 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/templates/partials/no_workspaces.html +2 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/templates/partials/pull_summary.html +2 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/templates/partials/repo_row.html +4 -1
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/templates/settings.html +2 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/templates/workspaces.html +2 -0
- gitstow-0.9.0/tests/__init__.py +4 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/tests/conftest.py +20 -0
- gitstow-0.9.0/tests/pull_invariant.py +66 -0
- gitstow-0.9.0/tests/test_cli.py +3194 -0
- gitstow-0.9.0/tests/test_clone_staging.py +368 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/tests/test_collection_io.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/tests/test_config.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/tests/test_diff.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/tests/test_git.py +242 -34
- gitstow-0.9.0/tests/test_git_env.py +105 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/tests/test_locking.py +11 -4
- {gitstow-0.7.2 → gitstow-0.9.0}/tests/test_mcp.py +124 -3
- {gitstow-0.7.2 → gitstow-0.9.0}/tests/test_move.py +51 -16
- {gitstow-0.7.2 → gitstow-0.9.0}/tests/test_onboard.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/tests/test_operations.py +33 -0
- gitstow-0.9.0/tests/test_path_rule.py +385 -0
- gitstow-0.9.0/tests/test_pull_safety.py +797 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/tests/test_repo.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/tests/test_serve.py +172 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/tests/test_setup_ai.py +3 -0
- gitstow-0.9.0/tests/test_skill_install.py +75 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/tests/test_status_model.py +3 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/tests/test_tailscale.py +3 -0
- gitstow-0.9.0/tests/test_url_parser.py +333 -0
- gitstow-0.7.2/BACKLOG.md +0 -44
- gitstow-0.7.2/LICENSE +0 -21
- gitstow-0.7.2/src/gitstow/__init__.py +0 -3
- gitstow-0.7.2/src/gitstow/cli/__init__.py +0 -1
- gitstow-0.7.2/src/gitstow/core/__init__.py +0 -1
- gitstow-0.7.2/src/gitstow/core/collection_io.py +0 -97
- gitstow-0.7.2/src/gitstow/mcp/__init__.py +0 -1
- gitstow-0.7.2/src/gitstow/web/routes/__init__.py +0 -1
- gitstow-0.7.2/src/gitstow/web/templates/partials/dashboard_rows.html +0 -1
- gitstow-0.7.2/tests/__init__.py +0 -1
- gitstow-0.7.2/tests/test_cli.py +0 -1503
- gitstow-0.7.2/tests/test_url_parser.py +0 -201
- {gitstow-0.7.2 → gitstow-0.9.0}/.claude/settings.json +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/.github/ISSUE_TEMPLATE/bug_report.yml +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/.github/ISSUE_TEMPLATE/feature_request.yml +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/.github/PULL_REQUEST_TEMPLATE.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/.github/workflows/ci.yml +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/.github/workflows/pages.yml +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/.github/workflows/publish.yml +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/.gitignore +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/AGENTS.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/CLAUDE.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/CODE_OF_CONDUCT.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/SECURITY.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/demo.gif +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/demo.tape +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/design_handoff_gitstow_landing/assets/demo.gif +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/design_handoff_gitstow_landing/assets/fonts/bricolage-grotesque-latin-var.woff2 +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/design_handoff_gitstow_landing/assets/fonts/jetbrains-mono-latin-var.woff2 +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/design_handoff_gitstow_landing/browser-window.jsx +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/design_handoff_gitstow_landing/screenshots/01-hero.png +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/design_handoff_gitstow_landing/screenshots/02-quick-start.png +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/design_handoff_gitstow_landing/screenshots/03-dashboard-showcase.png +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/design_handoff_gitstow_landing/screenshots/04-ai-integration.png +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/design_handoff_gitstow_landing/screenshots/05-feature-grid.png +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/design_handoff_gitstow_landing/screenshots/06-comparison.png +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/design_handoff_gitstow_landing/screenshots/07-cta-footer.png +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/building/audit-2026-07-06.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/building/plans/2026-07-06-wave-1-correctness-safety.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/building/plans/2026-07-06-wave-2-status-model.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/building/plans/2026-07-06-wave-3-structure-polish.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/building/plans/2026-07-12-ui-wave-a-make-it-real.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/building/plans/2026-07-12-ui-wave-b-polish.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/building/plans/2026-07-16-move-repo-between-workspaces.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/building/roadmap.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/building/ui-audit-2026-07-12.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/superpowers/plans/2026-07-19-diff-viewer.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/superpowers/plans/2026-08-11-tailscale-ui.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/superpowers/specs/2026-07-19-diff-viewer-design.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/superpowers/specs/2026-08-11-tailscale-ui-design.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/user/configuration.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/docs/user/getting-started.md +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/site/assets/demo.gif +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/site/assets/fonts/bricolage-grotesque-latin-var.woff2 +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/site/assets/fonts/jetbrains-mono-latin-var.woff2 +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/static/fonts/bricolage-grotesque-latin-ext-var.woff2 +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/static/fonts/bricolage-grotesque-latin-var.woff2 +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/static/fonts/fonts.css +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/static/fonts/jetbrains-mono-latin-ext-var.woff2 +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/static/fonts/jetbrains-mono-latin-var.woff2 +0 -0
- {gitstow-0.7.2 → gitstow-0.9.0}/src/gitstow/web/static/vendor/htmx.min.js +0 -0
gitstow-0.9.0/.mailmap
ADDED
|
@@ -0,0 +1 @@
|
|
|
1
|
+
rishmadaan <91198968+rishmadaan@users.noreply.github.com>
|
gitstow-0.9.0/BACKLOG.md
ADDED
|
@@ -0,0 +1,54 @@
|
|
|
1
|
+
# Backlog
|
|
2
|
+
|
|
3
|
+
Post-v0.1.0 improvements tracked here. See [GitHub Issues](https://github.com/rishmadaan/gitstow/issues) for discussion.
|
|
4
|
+
|
|
5
|
+
## Enhancements
|
|
6
|
+
|
|
7
|
+
- [x] **TUI: expand beyond read-only dashboard** (#1) — Added pull selected (P), workspace cycling (w), tag cycling (t)
|
|
8
|
+
- [x] **Shell completion for repo names** (#2) — `gitstow shell completions` for bash/zsh/fish; `--quiet` on list/tags/workspace list
|
|
9
|
+
- [x] **Network retry/resume for batch operations** (#3) — `--retry N` flag on add and pull; cleans up partial clones before retry
|
|
10
|
+
- [x] **Export format versioning and checksums** (#4) — Added `version: 1` to YAML/JSON exports; validates on import; backward-compatible with unversioned files
|
|
11
|
+
- [x] **Progress indication during long clones** (#5) — `git clone --progress`; pull shows live counter `[5/47]`
|
|
12
|
+
- [x] **Publish to PyPI** (#6) — Release workflow created (`.github/workflows/publish.yml`); publish on GitHub release
|
|
13
|
+
- [x] **Web dashboard (`gitstow ui`)** — Dark local browser UI wrapping core/ for daily repo management. FastAPI + Jinja2 + HTMX, dark + ember accent aesthetic. See [CHANGELOG.md](CHANGELOG.md) v0.2.0.
|
|
14
|
+
- [x] **Fix TUI breakage** — Resolved by retirement: the Textual TUI was removed in v0.3.0; `gitstow ui` (web dashboard) is the visual surface going forward.
|
|
15
|
+
|
|
16
|
+
## Documentation
|
|
17
|
+
|
|
18
|
+
- [x] **Record demo GIF for README** (#7) — Recorded with VHS, embedded in README
|
|
19
|
+
- [x] **Marketing landing page** — [gitstow.com](https://gitstow.com); static site in `site/`, auto-deployed by GitHub Pages on push to main
|
|
20
|
+
|
|
21
|
+
## Post-0.3.0 follow-ups
|
|
22
|
+
|
|
23
|
+
Triaged non-blocking items from the 2026-07 audit remediation (see
|
|
24
|
+
[docs/building/audit-2026-07-06.md](docs/building/audit-2026-07-06.md) for the full effort).
|
|
25
|
+
|
|
26
|
+
- [x] **URL parser: schemeless multi-dot hosts** — Fixed in 0.9.0: multi-dot hosts parse without a scheme, and Azure clone URLs now use Azure's `/_git/` and `v3/` forms. Was: `dev.azure.com/org/project/_git/repo` without
|
|
27
|
+
`https://` parses as owner/repo shorthand and builds a garbage clone URL (`_LOOKS_LIKE_HOST`
|
|
28
|
+
regex can't match a multi-dot first segment). Pre-existing; 0.3.1 candidate.
|
|
29
|
+
- [x] **Route search subprocesses through a hardened runner** — Done in 0.9.0: one `search_repo()` in `core/git.py` for CLI and MCP (shared env, `-e` pattern, glob in the git grep fallback). Was: `git grep`/`rg` in `cli/search.py`
|
|
30
|
+
and `mcp/server.py` shell raw `subprocess.run` without the `GIT_TERMINAL_PROMPT=0`/`LC_ALL=C`
|
|
31
|
+
env applied to all other git calls. Local-only operations, negligible risk — consistency cleanup.
|
|
32
|
+
- [x] **Test strengthening batch** — Done in 0.9.0: all four tests now fail against the bug they guard. Was: frozen-collapse MCP test needs two frozen same-named repos;
|
|
33
|
+
`run_bulk` missing-status retry + `on_attempt` callback untested; locking mutual-exclusion test
|
|
34
|
+
passes without a lock (use an event-based barrier); status JSON legacy-key test covers 3/13 keys.
|
|
35
|
+
- [x] **Small edges** — Fixed in 0.9.0 (the no-remote `add` case was a data-loss bug with `--retry`: the retry cleanup deleted the folder). Was: `add` on an on-disk repo with no remote falls through to a doomed clone;
|
|
36
|
+
whitespace-only `$EDITOR` raises IndexError; fully-untracked workspaces never get the untracked
|
|
37
|
+
hint (early return; `doctor` covers); dashboard vs single-row-refresh number sources diverge for
|
|
38
|
+
orphaned-workspace repos.
|
|
39
|
+
- [x] **Product call: `pull --force` escape hatch** — Added in 0.9.0 (CLI `--force`, for named repos only; a bulk `--force` is refused, and MCP has no force). Was: CLI explicit args follow the bulk skip rule
|
|
40
|
+
while a web single-row Pull click pulls unconditionally; a `--force` flag would reconcile the
|
|
41
|
+
"explicit intent" asymmetry.
|
|
42
|
+
- [x] **Product call: frozen + diverged + `--include-frozen`** — Fixed in 0.9.0: a clean "diverged" (or "local-only") skip. Was: surfaces as an ff-only error row
|
|
43
|
+
instead of a clean "diverged" skip (check `remote_state` directly in the worker if the messaging
|
|
44
|
+
matters).
|
|
45
|
+
|
|
46
|
+
## Post-0.9.0 follow-ups
|
|
47
|
+
|
|
48
|
+
- [ ] **Align MCP `add_repo` and the dashboard's Add with CLI `add` for an on-disk repo** — when the target folder is already a git repo, both register it with `remote_url` set to the URL that was asked for, without reading its real `origin`: a repo with no remote gets a guessed remote recorded, and one whose remote is a different project is registered with no mismatch error (MCP `add_repo` in `mcp/server.py`; dashboard `add_repo` in `web/routes/repos.py`, the `target.exists()` / `is_git_repo` branch). Not data loss (neither has a retry or deletes anything). CLI `add` refuses both cases since 0.9.0; share that classification so all three surfaces answer the same way.
|
|
49
|
+
- [ ] **The repo page's "Pull now" button does nothing** — `web/templates/_repo_drawer.html` renders `↓ Pull now` with no action attached, so pressing it has no effect. The planned incoming-changes viewer replaces it.
|
|
50
|
+
- [ ] **Collection imports register any existing folder without checking it** — `gitstow collection import` and the dashboard's import register an entry whose target path already exists, without checking that it is a git repo or that its `origin` matches the entry (`cli/export_cmd.py` and `web/routes/collection.py`, the `target.exists()` branch). Pre-existing; not data loss (nothing is cloned over or deleted). Share CLI `add`'s classification (not a git repo, no remote, remote mismatch) so imports refuse the same cases.
|
|
51
|
+
- [ ] **Repo identity reads `git remote get-url origin`** — that returns the URL after any `url.<base>.insteadOf` rewrite, so a repo cloned through a rewrite can look like a different repo (a false remote mismatch, or a missed "already tracked"), and a repo whose only remote is not named `origin` reads as "no remote" (`core/git.py` `get_remote_url`, used by `add`'s on-disk checks, `workspace scan` discovery, `migrate` and `open`). Pre-existing; no wrong delete. Read the configured `remote.origin.url` (or the single remote, whatever its name) instead.
|
|
52
|
+
- [ ] **`migrate --json` without `--quiet` prints progress ahead of the JSON** — the `✓ registered`, `Moving …` and `migrated` lines go to stdout before the JSON document (`cli/migrate.py`), so the output does not parse. Pre-existing. Send progress to stderr, or suppress it under `--json`, as the other commands do.
|
|
53
|
+
- [ ] **macOS CI skips the trailing-Unicode-whitespace branch names too** — `tests/test_pull_safety.py` skips both byte-name sweeps where the filesystem refuses non-UTF-8 names (macOS), which also drops the valid-UTF-8 names ending in U+3000/U+00A0/U+0085 that guard the old `.strip()` failure. Split valid-UTF-8 names from invalid-byte names and skip only the latter (0.9.0 review residue R6-C2; coverage only).
|
|
54
|
+
- [ ] **Naming a set-aside repo says "not tracked"** — `gitstow pull ../outside` prints "'../outside' not tracked. Skipping." when the entry is in repos.yaml but set aside as an unsafe path; say "'<key>' is set aside (not a safe folder path); see gitstow doctor" instead (`cli/pull.py` named-repo branch; 0.9.0 review residue R6-F1; wording only, nothing is pulled).
|
|
@@ -4,6 +4,48 @@ All notable changes to gitstow will be documented in this file.
|
|
|
4
4
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/), and this project adheres to [Semantic Versioning](https://semver.org/).
|
|
6
6
|
|
|
7
|
+
## [0.9.0] - 2026-11-20
|
|
8
|
+
|
|
9
|
+
### Fixed
|
|
10
|
+
|
|
11
|
+
- **`gitstow add` can no longer delete a local repo** — if the target folder already held a git repo with no `origin` remote (one you `git init`ed yourself), `add` treated it as a fresh clone; the clone failed on the non-empty folder, and with `--retry 1` or more the retry cleanup deleted the folder, your commits with it, before cloning again. That folder is now never cloned over: `add` stops with an error that gives the exact command to add the remote (`git -C <folder> remote add origin <url>`), after which the same `gitstow add` registers it as already on disk.
|
|
12
|
+
- **A URL, a collection or an old repos.yaml entry can no longer make gitstow act on a folder outside its workspace** — a URL with a `..` path segment (like `https://github.com/../Documents`) was accepted, so `gitstow collection import` or the dashboard's import could register the folder beside the workspace as a tracked repo, and the MCP `remove_repo` tool, which unlike `gitstow remove` and the dashboard did not check where a folder was, could then delete it. URLs whose owner or repo would not be a safe folder name (a `.`, `..` or empty path segment, a segment of only dots and spaces, or a `\`, `:` or control character, so `acme//widget`, `..\Documents` and `D:` too; a control character inside the URL is refused, not silently dropped; whitespace around the whole URL is trimmed first) are now refused as invalid. Entries already in repos.yaml with such a key (accepted by older versions, or written by hand) reached further: `gitstow pull` and `gitstow exec` could act on a repo outside the workspace, `gitstow config migrate-root` could move one, and removing an entry like `./widget` could delete the workspace folder. Such an entry is now set aside when repos.yaml is read: every command ignores it, it is kept unchanged in the file, and `gitstow doctor` lists it with what to do (`gitstow list` and `gitstow status` print a one-line reminder). Every delete or move (`gitstow remove --delete`, the repo page's "Remove + delete folder", `remove_repo`, `gitstow repo move`, `gitstow config migrate-root`, and `gitstow migrate`'s destination) refuses a folder that resolves outside its workspace, also through a symlink, and `gitstow workspace scan` skips (and lists) a repo folder whose name cannot be tracked safely.
|
|
13
|
+
- **Clones never replace or delete a folder with anything in it** — every clone, from `gitstow add`, the MCP `add_repo` tool, the dashboard's Add page and both collection imports (`gitstow collection import` and the dashboard's import), now runs in a hidden staging folder beside the target and is moved into place in one step only when it is complete. If something appeared at the target in the meantime (another gitstow command, the dashboard, or your own `git clone`), that repo fails with "already exists … left untouched" and whatever is there is kept (on Linux and macOS an empty folder at the target is simply replaced, as there is nothing in it to lose; on Windows that clone stops with "already exists"); a retry or a failed clone only ever cleans up its own staging folder, so a failed clone leaves no repo folder behind. Before, a failing `gitstow add --retry` cleared its target before each retry, which could delete a folder another add had filled in the meantime, local edits included.
|
|
14
|
+
- **Pulls never overwrite your local edits or ignored files, whatever your git settings for stashing, rebasing or merge options** — a pull never auto-stashes and re-applies your edits (with `merge.autoStash`, `pull.rebase` plus `rebase.autoStash`, or `--autostash` in a branch's `branch.<name>.mergeOptions`, git did that and could leave conflict markers in a file while reporting success), never lets a branch's merge options or a `pull.twohead` strategy turn it into a squash or a merge commit (with `pull.twohead=subtree` git could even overwrite an ignored local file and report success), and never overwrites an ignored local file (like a `.env`) when upstream starts tracking that path. In every case the pull is refused and the files are left as they were. gitstow does not stop programs you have told git to run during a pull, such as hooks, clean/smudge filters (Git LFS) or helpers chosen through your environment; those run as you configured them. A branch whose name contains `=` and that has merge options set is refused, since gitstow cannot switch them off for it; pull it with git. A branch whose upstream was deleted on the remote now gets a plain message ("the upstream branch no longer exists on the remote") instead of git's raw error, and so does a detached HEAD ("not on a branch") where a single repo is pulled directly (the dashboard's row Pull, `gitstow add --update`); bulk pulls skip a detached HEAD as a local-only repo, as before. This applies to `gitstow pull`, `gitstow add --update`, the MCP `pull_repos` tool and the dashboard's Pull buttons.
|
|
15
|
+
- **Azure DevOps URLs work** — `dev.azure.com/org/project/_git/repo` typed without `https://` was read as GitHub shorthand, and even with the scheme the clone URL was built in a form Azure does not serve. Clone URLs now use Azure's documented forms (`https://dev.azure.com/org/project/_git/repo`, or `git@ssh.dev.azure.com:v3/org/project/repo` with SSH preferred; legacy `org.visualstudio.com` URLs keep HTTPS, and the legacy SSH form `org@vs-ssh.visualstudio.com:v3/org/project/repo` clones by the `ssh.dev.azure.com` form), and the SSH and HTTPS forms are recognised as the same repo. Any host with several dots (e.g. `git.example.co.uk/group/repo`) is now recognised without a scheme too. Repos added by an HTTPS Azure URL keep their folders. Repos first added by the SSH `v3/` URL keep their `v3/...` folder and stay tracked, and adding them again by either URL form now finds the existing record instead of cloning a second copy.
|
|
16
|
+
- **Adding a repo that is already tracked never clones a second copy or resets it** — `gitstow add`, the MCP `add_repo` tool and the dashboard's Add page find the existing record, also when it is tracked under another URL form, and report it under its stored name (`gitstow add --update` pulls that folder); both collection imports skip it instead of cloning a second copy. The dashboard's Add page used to re-register an already-tracked repo, resetting its tags and frozen state. A collection that lists the same repo twice (say its HTTPS and SSH URLs) now imports it once and keeps the first entry's tags and frozen state, and an entry that would land in a folder already used by a different repo (another host, or another owner in a flat workspace) is not imported instead of being registered over it: `gitstow collection import` names the conflict, and the dashboard's import banner lists it with the reason (it used to count it as failed with no reason). An exported YAML or JSON file is judged by its URLs like a URL list; it used to match entries by their stored key, which skipped such a conflict as already tracked. `gitstow collection import --dry-run` lists each entry once with what it would do. If the tracked repo's folder has been deleted, `gitstow add`, `add_repo` and the Add page now say so and name the way out (remove it from gitstow: `gitstow remove <name>`, `remove_repo`, or Remove in the row's ⋯ menu; then add it again to re-clone) instead of answering "already tracked".
|
|
17
|
+
- **`gitstow pull` and `gitstow fetch` never act on a repo around a tracked folder** — if a tracked repo's `.git` was broken or empty and its workspace sits inside another git repo (say a workspace under a folder that is itself a repo), git looked in the folders above, so `gitstow pull` could fast-forward that outer repo and write its files. gitstow now tells git to stop at the repo's own folder, and `gitstow pull` and `gitstow fetch` first check that git sees the folder as the top of its own repository, so such a repo is reported as an error and the outer repo is left untouched.
|
|
18
|
+
- **gitstow run from inside a git hook no longer touches the wrong repo** — a git hook runs with `GIT_DIR`, `GIT_WORK_TREE` and similar variables set for its own repo, and git obeys them over the folder it is run in, so a `gitstow pull` started from a hook could fast-forward the hook's repo and write its files into another repo's folder. gitstow now drops those variables from every git command it runs, and from the commands `gitstow exec` runs, so each command acts on the repo it names. Git settings passed through the environment (`GIT_CONFIG_COUNT` with `GIT_CONFIG_KEY_<n>`/`GIT_CONFIG_VALUE_<n>`, `GIT_CONFIG_PARAMETERS`, `GIT_CONFIG`) are ignored by gitstow's git commands too; put them in a git config file instead.
|
|
19
|
+
- **The dashboard shows why a single-row Pull or Fetch failed** — when git refused a Pull (to protect a local file) or a Fetch failed, the row came back as if nothing had happened. Git's message now appears in the row, under the repo name, and the last-pulled time keeps its old value; the 30-second auto-refresh waits while the message is on screen; dismiss it with ×, or filter its row out and the next refresh clears it.
|
|
20
|
+
- **`gitstow search` handles patterns that start with `-`** — `gitstow search -- -foo` searches for `-foo` instead of passing it to ripgrep or git grep as an option, and `--glob` now also filters when ripgrep is not installed (the `git grep` fallback used to ignore it). The CLI and the MCP `search_repos` tool now share one search runner that drops inherited repository variables and disables terminal credential prompts (it keeps your locale, so case-insensitive search can match non-ASCII letters where your locale supports it).
|
|
21
|
+
- **Frozen repos that split from upstream show a clean skip** — `gitstow pull --include-frozen` on a frozen repo that has diverged from its remote (or has no upstream) now reports "skipped — Diverged from remote" (or "Local-only repo") like any other repo, instead of attempting a pull that could only fail and showing it as an error.
|
|
22
|
+
- **The "untracked repos" hint now appears when nothing is tracked yet** — `gitstow list` and `gitstow status` returned early on an empty result and never suggested `gitstow workspace scan`, so a workspace whose repos were all untracked never got the nudge. `gitstow list --json` with no results no longer prints a message ahead of the JSON, and `gitstow list --json --quiet` (the form the bundled Claude skill uses) now prints JSON; it used to print plain repo names whenever anything was tracked.
|
|
23
|
+
- **A blank `$VISUAL` or `$EDITOR` no longer crashes `gitstow open`** — a whitespace-only value counts as unset, so the next editor setting or the usual fallbacks are used.
|
|
24
|
+
- **Dashboard row numbers stay put after a single-row Pull, Fetch, freeze or tag** — the refreshed row used to be numbered counting records from workspaces that are no longer configured, so it could jump to a different number than the full page showed.
|
|
25
|
+
|
|
26
|
+
### Added
|
|
27
|
+
|
|
28
|
+
- **`gitstow pull owner/repo --force`** — also pulls the repos you name when they have modified or staged files, for when you have asked for a pull and mean it (the dashboard's single-row Pull already works this way). `--force` applies only to repos you name: `gitstow pull --force` with no names (filters such as `--tag` or `-w` do not count) stops with an error before pulling anything. Git's fast-forward-only pull still refuses any pull that would overwrite a modified file, and that refusal is reported as an error with your file untouched. Diverged and local-only repos are still skipped, and frozen repos still need `--include-frozen`.
|
|
29
|
+
- **MCP `pull_repos` rows for frozen repos now name their workspace** — `skipped_frozen` rows carry a `workspace` field, so two frozen repos with the same name in different workspaces can be told apart (the CLI's frozen rows already did this).
|
|
30
|
+
|
|
31
|
+
## [0.8.0] - 2026-09-13
|
|
32
|
+
|
|
33
|
+
### Changed
|
|
34
|
+
|
|
35
|
+
- License changed from MIT to GNU GPL v3.0 or later (`GPL-3.0-or-later`) for
|
|
36
|
+
versions after 0.7.2. Previously released versions retain their MIT license.
|
|
37
|
+
Commercial use remains permitted; redistribution of covered versions must
|
|
38
|
+
satisfy the GPL, including corresponding-source requirements. Repositories
|
|
39
|
+
managed by gitstow are unaffected. Bundled htmx and fonts retain their own
|
|
40
|
+
licenses, now included in both source and wheel distributions.
|
|
41
|
+
- Standardized author attribution as `rishmadaan`, including a Git mailmap for
|
|
42
|
+
historical author names without rewriting commits.
|
|
43
|
+
- The version is now `0.8.0`, distinct from the published
|
|
44
|
+
MIT-licensed 0.7.2. The installed Claude skill includes its GPL notice and
|
|
45
|
+
full license, including on automatic upgrades; an incomplete bundled skill
|
|
46
|
+
leaves the previous installation and version marker intact. The website
|
|
47
|
+
also ships its GPL terms and both font licenses.
|
|
48
|
+
|
|
7
49
|
## [0.7.2] - 2026-09-03
|
|
8
50
|
|
|
9
51
|
### Fixed
|
|
@@ -2,6 +2,14 @@
|
|
|
2
2
|
|
|
3
3
|
Thanks for your interest in contributing! This guide will help you get started.
|
|
4
4
|
|
|
5
|
+
## Contribution License
|
|
6
|
+
|
|
7
|
+
By submitting a contribution, you agree to license your original contribution
|
|
8
|
+
under the GNU General Public License v3.0 or later (`GPL-3.0-or-later`), as
|
|
9
|
+
described in [LICENSE](LICENSE) and [NOTICE](NOTICE). You retain your copyright.
|
|
10
|
+
Only submit work you have the right to contribute. Identify any third-party
|
|
11
|
+
material and preserve its license and copyright notices.
|
|
12
|
+
|
|
5
13
|
## Development Setup
|
|
6
14
|
|
|
7
15
|
```bash
|
gitstow-0.9.0/LICENSE
ADDED
|
@@ -0,0 +1,232 @@
|
|
|
1
|
+
GNU GENERAL PUBLIC LICENSE
|
|
2
|
+
Version 3, 29 June 2007
|
|
3
|
+
|
|
4
|
+
Copyright © 2007 Free Software Foundation, Inc. <https://fsf.org/>
|
|
5
|
+
|
|
6
|
+
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
|
|
7
|
+
|
|
8
|
+
Preamble
|
|
9
|
+
|
|
10
|
+
The GNU General Public License is a free, copyleft license for software and other kinds of works.
|
|
11
|
+
|
|
12
|
+
The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.
|
|
13
|
+
|
|
14
|
+
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
|
|
15
|
+
|
|
16
|
+
To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.
|
|
17
|
+
|
|
18
|
+
For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
|
|
19
|
+
|
|
20
|
+
Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.
|
|
21
|
+
|
|
22
|
+
For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.
|
|
23
|
+
|
|
24
|
+
Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.
|
|
25
|
+
|
|
26
|
+
Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.
|
|
27
|
+
|
|
28
|
+
The precise terms and conditions for copying, distribution and modification follow.
|
|
29
|
+
|
|
30
|
+
TERMS AND CONDITIONS
|
|
31
|
+
|
|
32
|
+
0. Definitions.
|
|
33
|
+
|
|
34
|
+
“This License” refers to version 3 of the GNU General Public License.
|
|
35
|
+
|
|
36
|
+
“Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
|
|
37
|
+
|
|
38
|
+
“The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.
|
|
39
|
+
|
|
40
|
+
To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.
|
|
41
|
+
|
|
42
|
+
A “covered work” means either the unmodified Program or a work based on the Program.
|
|
43
|
+
|
|
44
|
+
To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
|
|
45
|
+
|
|
46
|
+
To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
|
|
47
|
+
|
|
48
|
+
An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
|
|
49
|
+
|
|
50
|
+
1. Source Code.
|
|
51
|
+
The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.
|
|
52
|
+
|
|
53
|
+
A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
|
|
54
|
+
|
|
55
|
+
The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
|
|
56
|
+
|
|
57
|
+
The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
|
|
58
|
+
|
|
59
|
+
The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
|
|
60
|
+
|
|
61
|
+
The Corresponding Source for a work in source code form is that same work.
|
|
62
|
+
|
|
63
|
+
2. Basic Permissions.
|
|
64
|
+
All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
|
|
65
|
+
|
|
66
|
+
You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
|
|
67
|
+
|
|
68
|
+
Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
|
|
69
|
+
|
|
70
|
+
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
|
|
71
|
+
No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
|
|
72
|
+
|
|
73
|
+
When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
|
|
74
|
+
|
|
75
|
+
4. Conveying Verbatim Copies.
|
|
76
|
+
You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
|
|
77
|
+
|
|
78
|
+
You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
|
|
79
|
+
|
|
80
|
+
5. Conveying Modified Source Versions.
|
|
81
|
+
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
|
|
82
|
+
|
|
83
|
+
a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
|
|
84
|
+
|
|
85
|
+
b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.
|
|
86
|
+
|
|
87
|
+
c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
|
|
88
|
+
|
|
89
|
+
d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
|
|
90
|
+
|
|
91
|
+
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
|
|
92
|
+
|
|
93
|
+
6. Conveying Non-Source Forms.
|
|
94
|
+
You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
|
|
95
|
+
|
|
96
|
+
a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
|
|
97
|
+
|
|
98
|
+
b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
|
|
99
|
+
|
|
100
|
+
c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
|
|
101
|
+
|
|
102
|
+
d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
|
|
103
|
+
|
|
104
|
+
e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
|
|
105
|
+
|
|
106
|
+
A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
|
|
107
|
+
|
|
108
|
+
A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
|
|
109
|
+
|
|
110
|
+
“Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
|
|
111
|
+
|
|
112
|
+
If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
|
|
113
|
+
|
|
114
|
+
The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
|
|
115
|
+
|
|
116
|
+
Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
|
|
117
|
+
|
|
118
|
+
7. Additional Terms.
|
|
119
|
+
“Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
|
|
120
|
+
|
|
121
|
+
When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
|
|
122
|
+
|
|
123
|
+
Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
|
|
124
|
+
|
|
125
|
+
a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
|
|
126
|
+
|
|
127
|
+
b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
|
|
128
|
+
|
|
129
|
+
c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
|
|
130
|
+
|
|
131
|
+
d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
|
|
132
|
+
|
|
133
|
+
e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
|
|
134
|
+
|
|
135
|
+
f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
|
|
136
|
+
|
|
137
|
+
All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
|
|
138
|
+
|
|
139
|
+
If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
|
|
140
|
+
|
|
141
|
+
Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
|
|
142
|
+
|
|
143
|
+
8. Termination.
|
|
144
|
+
You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
|
|
145
|
+
|
|
146
|
+
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
|
|
147
|
+
|
|
148
|
+
Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
|
|
149
|
+
|
|
150
|
+
Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
|
|
151
|
+
|
|
152
|
+
9. Acceptance Not Required for Having Copies.
|
|
153
|
+
You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
|
|
154
|
+
|
|
155
|
+
10. Automatic Licensing of Downstream Recipients.
|
|
156
|
+
Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.
|
|
157
|
+
|
|
158
|
+
An “entity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
|
|
159
|
+
|
|
160
|
+
You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
|
|
161
|
+
|
|
162
|
+
11. Patents.
|
|
163
|
+
A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's “contributor version”.
|
|
164
|
+
|
|
165
|
+
A contributor's “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
|
|
166
|
+
|
|
167
|
+
Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
|
|
168
|
+
|
|
169
|
+
In the following three paragraphs, a “patent license” is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To “grant” such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
|
|
170
|
+
|
|
171
|
+
If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. “Knowingly relying” means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
|
|
172
|
+
|
|
173
|
+
If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
|
|
174
|
+
|
|
175
|
+
A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
|
|
176
|
+
|
|
177
|
+
Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
|
|
178
|
+
|
|
179
|
+
12. No Surrender of Others' Freedom.
|
|
180
|
+
If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
|
|
181
|
+
|
|
182
|
+
13. Use with the GNU Affero General Public License.
|
|
183
|
+
Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.
|
|
184
|
+
|
|
185
|
+
14. Revised Versions of this License.
|
|
186
|
+
The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
|
|
187
|
+
|
|
188
|
+
Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.
|
|
189
|
+
|
|
190
|
+
If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
|
|
191
|
+
|
|
192
|
+
Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
|
|
193
|
+
|
|
194
|
+
15. Disclaimer of Warranty.
|
|
195
|
+
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
|
|
196
|
+
|
|
197
|
+
16. Limitation of Liability.
|
|
198
|
+
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
|
|
199
|
+
|
|
200
|
+
17. Interpretation of Sections 15 and 16.
|
|
201
|
+
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
|
|
202
|
+
|
|
203
|
+
END OF TERMS AND CONDITIONS
|
|
204
|
+
|
|
205
|
+
How to Apply These Terms to Your New Programs
|
|
206
|
+
|
|
207
|
+
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
|
|
208
|
+
|
|
209
|
+
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.
|
|
210
|
+
|
|
211
|
+
<one line to give the program's name and a brief idea of what it does.>
|
|
212
|
+
Copyright (C) <year> <name of author>
|
|
213
|
+
|
|
214
|
+
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
|
|
215
|
+
|
|
216
|
+
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
|
|
217
|
+
|
|
218
|
+
You should have received a copy of the GNU General Public License along with this program. If not, see <https://www.gnu.org/licenses/>.
|
|
219
|
+
|
|
220
|
+
Also add information on how to contact you by electronic and paper mail.
|
|
221
|
+
|
|
222
|
+
If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
|
|
223
|
+
|
|
224
|
+
<program> Copyright (C) <year> <name of author>
|
|
225
|
+
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
|
|
226
|
+
This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.
|
|
227
|
+
|
|
228
|
+
The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an “about box”.
|
|
229
|
+
|
|
230
|
+
You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <https://www.gnu.org/licenses/>.
|
|
231
|
+
|
|
232
|
+
The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <https://www.gnu.org/philosophy/why-not-lgpl.html>.
|
gitstow-0.9.0/NOTICE
ADDED
|
@@ -0,0 +1,36 @@
|
|
|
1
|
+
gitstow
|
|
2
|
+
Copyright (c) 2026 rishmadaan
|
|
3
|
+
|
|
4
|
+
gitstow's original code, documentation, and website are free software: you
|
|
5
|
+
can redistribute them and/or modify them under the terms of the GNU General
|
|
6
|
+
Public License as published by the Free Software Foundation, either version 3
|
|
7
|
+
of the License, or (at your option) any later version.
|
|
8
|
+
|
|
9
|
+
gitstow is distributed in the hope that it will be useful, but WITHOUT ANY
|
|
10
|
+
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR
|
|
11
|
+
A PARTICULAR PURPOSE. See the GNU General Public License for more details.
|
|
12
|
+
|
|
13
|
+
You should have received a copy of the GNU General Public License along with
|
|
14
|
+
gitstow, in LICENSE. If not, see <https://www.gnu.org/licenses/>.
|
|
15
|
+
|
|
16
|
+
Source: https://github.com/rishmadaan/gitstow
|
|
17
|
+
|
|
18
|
+
Versions through 0.7.2 were released under the MIT license. Those releases
|
|
19
|
+
retain their original license. The transition applies to subsequent versions,
|
|
20
|
+
starting with version 0.8.0.
|
|
21
|
+
The author names Rish and Rish Madaan refer to rishmadaan.
|
|
22
|
+
|
|
23
|
+
Third-party assets retain their original licenses:
|
|
24
|
+
|
|
25
|
+
- htmx 1.9.10: BSD-2-Clause. Copyright (c) 2020, Big Sky Software.
|
|
26
|
+
See src/gitstow/web/static/vendor/LICENSE-htmx.txt.
|
|
27
|
+
- Bricolage Grotesque fonts: OFL-1.1.
|
|
28
|
+
Copyright 2022 The Bricolage Grotesque Project Authors.
|
|
29
|
+
See src/gitstow/web/static/fonts/OFL-bricolage-grotesque.txt.
|
|
30
|
+
- JetBrains Mono fonts: OFL-1.1.
|
|
31
|
+
Copyright 2020 The JetBrains Mono Project Authors.
|
|
32
|
+
See src/gitstow/web/static/fonts/OFL-jetbrains-mono.txt.
|
|
33
|
+
|
|
34
|
+
The distribution's SPDX expression includes these bundled components using
|
|
35
|
+
AND. It does not offer a choice of licenses for gitstow's original code.
|
|
36
|
+
Separately installed Python dependencies retain their respective licenses.
|
|
@@ -1,20 +1,23 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: gitstow
|
|
3
|
-
Version: 0.
|
|
3
|
+
Version: 0.9.0
|
|
4
4
|
Summary: A git repository library manager — clone, organize, and maintain collections of repos you learn from
|
|
5
5
|
Project-URL: Homepage, https://gitstow.com
|
|
6
6
|
Project-URL: Repository, https://github.com/rishmadaan/gitstow
|
|
7
7
|
Project-URL: Documentation, https://github.com/rishmadaan/gitstow#readme
|
|
8
8
|
Project-URL: Issues, https://github.com/rishmadaan/gitstow/issues
|
|
9
9
|
Project-URL: Changelog, https://github.com/rishmadaan/gitstow/blob/main/CHANGELOG.md
|
|
10
|
-
Author:
|
|
11
|
-
License-Expression:
|
|
10
|
+
Author: rishmadaan
|
|
11
|
+
License-Expression: GPL-3.0-or-later AND BSD-2-Clause AND OFL-1.1
|
|
12
12
|
License-File: LICENSE
|
|
13
|
+
License-File: NOTICE
|
|
14
|
+
License-File: src/gitstow/web/static/fonts/OFL-bricolage-grotesque.txt
|
|
15
|
+
License-File: src/gitstow/web/static/fonts/OFL-jetbrains-mono.txt
|
|
16
|
+
License-File: src/gitstow/web/static/vendor/LICENSE-htmx.txt
|
|
13
17
|
Keywords: cli,developer-tools,git,manager,open-source,repository
|
|
14
18
|
Classifier: Development Status :: 3 - Alpha
|
|
15
19
|
Classifier: Environment :: Console
|
|
16
20
|
Classifier: Intended Audience :: Developers
|
|
17
|
-
Classifier: License :: OSI Approved :: MIT License
|
|
18
21
|
Classifier: Operating System :: MacOS
|
|
19
22
|
Classifier: Operating System :: Microsoft :: Windows
|
|
20
23
|
Classifier: Operating System :: POSIX :: Linux
|
|
@@ -126,6 +129,7 @@ gitstow pull # Update all repos across all workspaces
|
|
|
126
129
|
gitstow -w oss pull # Only update oss workspace
|
|
127
130
|
gitstow pull --tag ai # Only repos tagged 'ai'
|
|
128
131
|
gitstow pull --exclude-tag stale # Everything except stale repos
|
|
132
|
+
gitstow pull owner/repo --force # Pull this repo even with modified files (git still refuses to overwrite them)
|
|
129
133
|
gitstow status # Git status dashboard
|
|
130
134
|
gitstow -w active status --dirty # Repos with local changes in active workspace
|
|
131
135
|
gitstow diff <repo> # View a repo's uncommitted changes (staged/unstaged) — view-only
|
|
@@ -331,7 +335,7 @@ Flat workspaces skip the owner directory entirely — repos are just `workspace/
|
|
|
331
335
|
|
|
332
336
|
**Workspace directory doesn't exist** — Run `gitstow doctor` to check workspace health. Create missing directories or update the path with `gitstow workspace add`.
|
|
333
337
|
|
|
334
|
-
**`gitstow doctor`** — Run this first when something isn't working. It checks git installation, config files, and workspace integrity.
|
|
338
|
+
**`gitstow doctor`** — Run this first when something isn't working. It checks git installation, config files, and workspace integrity, and lists any repos.yaml entry it set aside because its key is not a safe folder path.
|
|
335
339
|
|
|
336
340
|
## Development
|
|
337
341
|
|
|
@@ -356,4 +360,15 @@ See [CONTRIBUTING.md](CONTRIBUTING.md) for the full guide.
|
|
|
356
360
|
|
|
357
361
|
## License
|
|
358
362
|
|
|
359
|
-
|
|
363
|
+
Copyright (c) 2026 rishmadaan. Licensed under the
|
|
364
|
+
[GNU General Public License v3.0 or later](LICENSE) (`GPL-3.0-or-later`).
|
|
365
|
+
|
|
366
|
+
You may use gitstow commercially and modify it. When distributing covered
|
|
367
|
+
versions, you must comply with the GPL, including its corresponding-source
|
|
368
|
+
requirements. Simply managing a repository with gitstow does not change that
|
|
369
|
+
repository's license.
|
|
370
|
+
|
|
371
|
+
Versions through 0.7.2 remain MIT-licensed; subsequent versions use GPL v3 or
|
|
372
|
+
later, starting with version 0.8.0. Bundled htmx and fonts
|
|
373
|
+
retain their BSD and SIL Open Font licenses;
|
|
374
|
+
see [NOTICE](NOTICE) for attribution and scope.
|
|
@@ -81,6 +81,7 @@ gitstow pull # Update all repos across all workspaces
|
|
|
81
81
|
gitstow -w oss pull # Only update oss workspace
|
|
82
82
|
gitstow pull --tag ai # Only repos tagged 'ai'
|
|
83
83
|
gitstow pull --exclude-tag stale # Everything except stale repos
|
|
84
|
+
gitstow pull owner/repo --force # Pull this repo even with modified files (git still refuses to overwrite them)
|
|
84
85
|
gitstow status # Git status dashboard
|
|
85
86
|
gitstow -w active status --dirty # Repos with local changes in active workspace
|
|
86
87
|
gitstow diff <repo> # View a repo's uncommitted changes (staged/unstaged) — view-only
|
|
@@ -286,7 +287,7 @@ Flat workspaces skip the owner directory entirely — repos are just `workspace/
|
|
|
286
287
|
|
|
287
288
|
**Workspace directory doesn't exist** — Run `gitstow doctor` to check workspace health. Create missing directories or update the path with `gitstow workspace add`.
|
|
288
289
|
|
|
289
|
-
**`gitstow doctor`** — Run this first when something isn't working. It checks git installation, config files, and workspace integrity.
|
|
290
|
+
**`gitstow doctor`** — Run this first when something isn't working. It checks git installation, config files, and workspace integrity, and lists any repos.yaml entry it set aside because its key is not a safe folder path.
|
|
290
291
|
|
|
291
292
|
## Development
|
|
292
293
|
|
|
@@ -311,4 +312,15 @@ See [CONTRIBUTING.md](CONTRIBUTING.md) for the full guide.
|
|
|
311
312
|
|
|
312
313
|
## License
|
|
313
314
|
|
|
314
|
-
|
|
315
|
+
Copyright (c) 2026 rishmadaan. Licensed under the
|
|
316
|
+
[GNU General Public License v3.0 or later](LICENSE) (`GPL-3.0-or-later`).
|
|
317
|
+
|
|
318
|
+
You may use gitstow commercially and modify it. When distributing covered
|
|
319
|
+
versions, you must comply with the GPL, including its corresponding-source
|
|
320
|
+
requirements. Simply managing a repository with gitstow does not change that
|
|
321
|
+
repository's license.
|
|
322
|
+
|
|
323
|
+
Versions through 0.7.2 remain MIT-licensed; subsequent versions use GPL v3 or
|
|
324
|
+
later, starting with version 0.8.0. Bundled htmx and fonts
|
|
325
|
+
retain their BSD and SIL Open Font licenses;
|
|
326
|
+
see [NOTICE](NOTICE) for attribution and scope.
|
|
@@ -62,7 +62,7 @@ a:hover { color: #ff8457; text-decoration: underline; text-underline-offset: 3px
|
|
|
62
62
|
</div>
|
|
63
63
|
<a href="https://github.com/rishmadaan/gitstow" style="display: inline-flex; align-items: center; gap: 8px; padding: 13px 22px; border-radius: 3px; background: #ff6b35; color: #120500; font-weight: 600; font-size: 15px; text-decoration: none;" style-hover="background: #ff8457; box-shadow: 0 0 24px rgba(255,107,53,0.3); text-decoration: none; color: #120500;">Star on GitHub ↗</a>
|
|
64
64
|
</div>
|
|
65
|
-
<div style="margin-top: 28px; font-family: 'JetBrains Mono', monospace; font-size: 12px; color: #545962;">
|
|
65
|
+
<div style="margin-top: 28px; font-family: 'JetBrains Mono', monospace; font-size: 12px; color: #545962;">GPL v3 or later · Python 3.10+ · GitHub / GitLab / Bitbucket / Codeberg</div>
|
|
66
66
|
</section>
|
|
67
67
|
|
|
68
68
|
<section id="install" data-screen-label="Quick start" style="border-top: 1px solid #1c1f24;">
|
|
@@ -311,7 +311,7 @@ a:hover { color: #ff8457; text-decoration: underline; text-underline-offset: 3px
|
|
|
311
311
|
</div>
|
|
312
312
|
<div style="border-top: 1px solid #1c1f24;">
|
|
313
313
|
<div style="max-width: 1260px; margin: 0 auto; padding: 16px 32px; display: flex; justify-content: space-between; align-items: center; gap: 16px; flex-wrap: wrap; font-family: 'JetBrains Mono', monospace; font-size: 11.5px; color: #545962;">
|
|
314
|
-
<span>© 2026 ·
|
|
314
|
+
<span>© 2026 · <a href="../site/NOTICE.txt">GPL v3 or later</a></span>
|
|
315
315
|
<span>clone responsibly.</span>
|
|
316
316
|
</div>
|
|
317
317
|
</div>
|
|
@@ -32,7 +32,7 @@ One page, max content width 1260px (32px side padding), sections separated by 1p
|
|
|
32
32
|
Sticky top, `rgba(11,12,14,0.82)` + `backdrop-filter: blur(12px) saturate(160%)`, 1px bottom border. Left: 7px pulsing accent dot (2.2s box-shadow ring animation), "gitstow" wordmark (Bricolage 22px, wdth 85, wght 700), mono tagline "git library manager" behind a 1px left border. Right: uppercase mono-ish links (12px, letter-spacing 0.15em, muted → white on hover): Install, Dashboard, AI, Features, Compare (anchor links, smooth scroll), plus outlined "GitHub ↗" button (border `#32363d`; hover: accent border/text + `rgba(255,107,53,0.16)` bg).
|
|
33
33
|
|
|
34
34
|
### 2. Hero (centered)
|
|
35
|
-
Padding 96px top / 88px bottom. Eyebrow "a git repository library manager" flanked by two accent bars. ASCII-art "GITSTOW" in a `<pre>` (JetBrains Mono, `clamp(8px, 1.5vw, 16px)`, line-height 1.18, color accent, `text-shadow: 0 0 32px rgba(255,107,53,0.35)`, user-select none) — exact art is in the design file. H1 40px: "Clone it. Stow it. **Never lose it.**" (last phrase accent). Lede paragraph (17px, max 620px, contains inline `code` chip `~/misc-stuff-2`). CTA row: command bar (`#121418` bg, `#32363d` border, mono 15px: dim `$` + white `pipx install "gitstow[ui]"` + copy button) and solid accent button "Star on GitHub ↗" (hover: `#ff8457` + glow shadow). Below, mono 12px dim meta: `
|
|
35
|
+
Padding 96px top / 88px bottom. Eyebrow "a git repository library manager" flanked by two accent bars. ASCII-art "GITSTOW" in a `<pre>` (JetBrains Mono, `clamp(8px, 1.5vw, 16px)`, line-height 1.18, color accent, `text-shadow: 0 0 32px rgba(255,107,53,0.35)`, user-select none) — exact art is in the design file. H1 40px: "Clone it. Stow it. **Never lose it.**" (last phrase accent). Lede paragraph (17px, max 620px, contains inline `code` chip `~/misc-stuff-2`). CTA row: command bar (`#121418` bg, `#32363d` border, mono 15px: dim `$` + white `pipx install "gitstow[ui]"` + copy button) and solid accent button "Star on GitHub ↗" (hover: `#ff8457` + glow shadow). Below, mono 12px dim meta: `GPL v3 or later · Python 3.10+ · GitHub / GitLab / Bitbucket / Codeberg`.
|
|
36
36
|
|
|
37
37
|
Copy button pattern (used 3×: hero, quick-start, final CTA): 1px `#32363d` border, mono 11px uppercase "COPY", hover accent; on click writes command to clipboard and shows "COPIED ✓" for 1.6s.
|
|
38
38
|
|
|
@@ -70,7 +70,7 @@ Header: eyebrow "vs the field", h2 "The best of both. Then some.", paragraph. Bo
|
|
|
70
70
|
Centered, 96px padding, bottom radial accent glow. H2 44px: "Stop losing repos. / Start **stowing** them." Sub: "Your future self, and your agents, will thank you." Command bar with copy button (same pattern, 16px mono).
|
|
71
71
|
|
|
72
72
|
### 9. Footer
|
|
73
|
-
Top block: brand (dot + wordmark + "A git repository library manager, built for the age of AI-assisted development.") and two link columns (mono uppercase 10.5px column labels; 13.5px muted links, accent on hover): **Docs** → getting-started / commands / concepts / configuration (GitHub blob URLs), **Project** → GitHub, PyPI, Changelog, Contributing. Bottom bar behind 1px divider, mono 11.5px dim: "© 2026 ·
|
|
73
|
+
Top block: brand (dot + wordmark + "A git repository library manager, built for the age of AI-assisted development.") and two link columns (mono uppercase 10.5px column labels; 13.5px muted links, accent on hover): **Docs** → getting-started / commands / concepts / configuration (GitHub blob URLs), **Project** → GitHub, PyPI, Changelog, Contributing. Bottom bar behind 1px divider, mono 11.5px dim: "© 2026 · GPL v3 or later" left (the reference links to `../site/NOTICE.txt`; the deployed page uses `NOTICE.txt`), "clone responsibly." right.
|
|
74
74
|
|
|
75
75
|
## Interactions & Behavior
|
|
76
76
|
- Anchor nav with `scroll-behavior: smooth`.
|
|
@@ -71,7 +71,7 @@ gitstow (CLI)
|
|
|
71
71
|
├── pyproject.toml # Hatchling build, dependencies, entry point
|
|
72
72
|
├── README.md # User-facing docs
|
|
73
73
|
├── CLAUDE.md # AI developer instructions
|
|
74
|
-
├── LICENSE #
|
|
74
|
+
├── LICENSE # GPL-3.0-or-later
|
|
75
75
|
├── docs/
|
|
76
76
|
│ ├── user/
|
|
77
77
|
│ │ └── getting-started.md # Quick start guide
|