feat: forge.py for the short PR template, the sign-in in Tooling's own folder, one release.py, and new pr commands #24

Merged
HumanBean merged 3 commits from HumanBean/Tooling:refactor/process-and-release into main 2026-11-19 22:04:36 +00:00
Owner

Summary

Tooling's half of Longshot's docs, tools and process revamp (Longshot#1802):

  • forge.py follows Longshot's short PR template. pr status shows Testing (Tested, Still to test) and the three checklists by the repository module's names. pr merge refuses while a Ready to merge box is unticked (--force as for pr ready). Unused flags and stale text go; docs/forge.md is shorter.
  • The sign-in moves out of Longshot's folder. It was in %APPDATA%\Longshot on Windows, beside the game's saves. It now lives in ~/.config/magicbean or %LOCALAPPDATA%\MagicBean. It moves on its next write and is never copied, because the refresh token works once. A link stays at the old Linux path.
  • One release.py for Longshot and LongshotLauncher, here in scripts/. Each repository pins it with .tooling-rev.
  • New forge.py commands the skills asked for: pr review N --dismiss, pr list --json, pr push N, and release whats-new.
  • Skills (review, release, farm-run, team-updates) are shorter, follow the current tools and Longshot's process, and use these commands.

Testing

Tested: no tests run on this PC; static checks only (compile, --help). New tests: tests/test_config_move.py, tests/test_release.py, and new cases in tests/test_forge_pr.py.

Still to test:

  • Tooling's tests on Linux and Windows, with Longshot#1802's checkout beside it as LONGSHOT=, by hand or CI.
  • The sign-in move on Windows and Linux: a renewal moves forge.json, and an older copy still finds it on Linux, by hand.

Risks

  • Merge order: this merges with Longshot#1802, whose PR checker it expects. Then .tooling-rev in Longshot and the launcher gets this merge's commit.
  • Older Tooling on Windows: after the sign-in moves, an older Tooling copy asks you to sign in once.

🤖 Generated with Claude Code

## Summary Tooling's half of Longshot's docs, tools and process revamp ([Longshot#1802](https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/1802)): - **forge.py follows Longshot's short PR template.** `pr status` shows Testing (Tested, Still to test) and the three checklists by the repository module's names. `pr merge` refuses while a *Ready to merge* box is unticked (`--force` as for `pr ready`). Unused flags and stale text go; `docs/forge.md` is shorter. - **The sign-in moves out of Longshot's folder.** It was in `%APPDATA%\Longshot` on Windows, beside the game's saves. It now lives in `~/.config/magicbean` or `%LOCALAPPDATA%\MagicBean`. It moves on its next write and is never copied, because the refresh token works once. A link stays at the old Linux path. - **One `release.py`** for Longshot and LongshotLauncher, here in `scripts/`. Each repository pins it with `.tooling-rev`. - **New forge.py commands** the skills asked for: `pr review N --dismiss`, `pr list --json`, `pr push N`, and `release whats-new`. - **Skills** (review, release, farm-run, team-updates) are shorter, follow the current tools and Longshot's process, and use these commands. ## Testing **Tested:** no tests run on this PC; static checks only (compile, `--help`). New tests: `tests/test_config_move.py`, `tests/test_release.py`, and new cases in `tests/test_forge_pr.py`. **Still to test:** - Tooling's tests on Linux and Windows, with Longshot#1802's checkout beside it as `LONGSHOT=`, by hand or CI. - The sign-in move on Windows and Linux: a renewal moves `forge.json`, and an older copy still finds it on Linux, by hand. ## Risks - **Merge order:** this merges with Longshot#1802, whose PR checker it expects. Then `.tooling-rev` in Longshot and the launcher gets this merge's commit. - **Older Tooling on Windows:** after the sign-in moves, an older Tooling copy asks you to sign in once. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Member

Possibly related, for context:

  • PR MagicBeanDev/Longshot#1802 WIP: refactor(dev): docs, tools and process revamp: one dev.py, dev.py ab, one dev folder, a short PR template, faster dev builds — Companion PR; short template/checker dependency and merge order
  • PR #14 feat(forge): pr merge squash-merges a ready, passing pull request; pr checks and pr diff — Existing forge.py merge/check commands this change builds on
Possibly related, for context: - PR MagicBeanDev/Longshot#1802 WIP: refactor(dev): docs, tools and process revamp: one dev.py, dev.py ab, one dev folder, a short PR template, faster dev builds — Companion PR; short template/checker dependency and merge order - PR #14 feat(forge): pr merge squash-merges a ready, passing pull request; pr checks and pr diff — Existing forge.py merge/check commands this change builds on
HumanBean changed title from WIP: feat: forge.py for the short PR template, the sign-in in Tooling's own folder, one release.py, and new pr commands to feat: forge.py for the short PR template, the sign-in in Tooling's own folder, one release.py, and new pr commands 2026-11-19 22:04:31 +00:00
HumanBean deleted branch refactor/process-and-release 2026-11-19 22:04:36 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Tooling!24
No description provided.