chore(tools): test requests for Longshot's pull requests on git.magicbean.dev #5

Merged

HumanBean merged 1 commit from HumanBean/Longshot:forgejo-test-requests into main 2026-11-12 21:41:38 +00:00

Conversation 0 Commits 1 Files changed 5 +87 -75

HumanBean commented 2026-11-12 21:28:46 +00:00

Owner

• Copy link
• Copy Markdown

Test requests are moving from Hookshot's GitHub to Longshot on git.magicbean.dev, so the scripts and guides have to name Longshot's pull requests there and post results there.

Uses forge.py and the team sign-in from #3.

• scripts/test_requests.py: a request links to https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/<n>, and done takes a comment link on that PR (#issuecomment-…). The PR's state and labels come from git.magicbean.dev. A request is approved when the PR's author may push to Longshot (checked with the team sign-in), or the PR has the testing wanted label (now a label on Longshot). Same replay rules as the relay, which already reads these links.
• Testers check out a PR with forge.py pr checkout <n> and comment with forge.py pr comment <n> --body-file …; the comment link it prints is what done takes. docs/test-requests.md and the testing and request-testing skills say so, and setup is now one step: forge.py login.
• tests/test_test_requests.py follows the new links and approval; it passes.

On the server side (not in this repository) the relay already shows Longshot requests in the MagicBean server's #test-requests, approves them through Forgejo, posts a request for a PR when the label is added, and updates within seconds through a Forgejo webhook. Requests for Hookshot's GitHub PRs show as closed.

Test requests are moving from Hookshot's GitHub to Longshot on git.magicbean.dev, so the scripts and guides have to name Longshot's pull requests there and post results there. Uses `forge.py` and the team sign-in from #3. - `scripts/test_requests.py`: a request links to `https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/<n>`, and `done` takes a comment link on that PR (`#issuecomment-…`). The PR's state and labels come from git.magicbean.dev. A request is approved when the PR's author may push to Longshot (checked with the team sign-in), or the PR has the `testing wanted` label (now a label on Longshot). Same replay rules as the relay, which already reads these links. - Testers check out a PR with `forge.py pr checkout <n>` and comment with `forge.py pr comment <n> --body-file …`; the comment link it prints is what `done` takes. `docs/test-requests.md` and the `testing` and `request-testing` skills say so, and setup is now one step: `forge.py login`. - `tests/test_test_requests.py` follows the new links and approval; it passes. On the server side (not in this repository) the relay already shows Longshot requests in the MagicBean server's #test-requests, approves them through Forgejo, posts a request for a PR when the label is added, and updates within seconds through a Forgejo webhook. Requests for Hookshot's GitHub PRs show as closed.

HumanBean added 2 commits 2026-11-12 21:28:46 +00:00

Forgejo tooling: one sign-in for git and the team chat, scripts/forge.py for forks, pull requests and issues ... 3964f97325

Everything on magicbean.dev signs in through Forgejo, so there is now one sign-in: Sign in with Discord on
git.magicbean.dev gives a git token (Forgejo's built-in OAuth application for git, PKCE, nothing secret in the
repository), and the team chat's session comes from that token through the team's sign-in service, without a second
trip through the browser. scripts/magicbean_login.py, used by team_chat.py, test_requests.py and forge.py.

scripts/forge.py: login makes the person's fork of Longshot, adds the remotes forge (fetch) and forge-fork (push), and
serves as git's credential helper for git.magicbean.dev; pr create|list|view|comment|checkout and
issue list|view|create|comment. docs/forge.md is the guide for people (fj, the Forgejo CLI, as an option); AGENTS.md
has the steps for agents.

chore(tools): test requests for Longshot's pull requests on git.magicbean.dev ... 8196ae5a3b

Test requests now name Longshot's pull requests on git.magicbean.dev: scripts/test_requests.py reads a PR's state and
labels there, and approves a request when its author may push to Longshot or the PR has the testing wanted label (the
author check uses the team sign-in). Results go on the PR as a comment with forge.py pr comment, and done takes that
comment's link. The testing guide and the testing and request-testing skills use forge.py instead of gh.

HumanBean force-pushed forgejo-test-requests from 8196ae5a3b to 6d01fc94a3 2026-11-12 21:34:10 +00:00 Compare

HumanBean merged commit 8f7d0d37b4 into main 2026-11-12 21:41:38 +00:00

HumanBean deleted branch forgejo-test-requests 2026-11-12 21:41:38 +00:00

HumanBean referenced this pull request from a commit 2026-11-12 21:41:39 +00:00

chore(tools): test requests for Longshot's pull requests on git.magicbean.dev (#5)

HumanBean referenced this pull request 2026-11-12 22:00:18 +00:00

docs: point links to the project's history back at NotRexed/Hookshot #9

HumanBean referenced this pull request from a commit 2026-11-12 22:01:51 +00:00

docs: point links to the project's history back at NotRexed/Hookshot (#9)

mooki referenced this pull request 2026-11-12 23:57:12 +00:00

Idea: opt-in hardware tests on self-hosted Forgejo runners #43

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

accessibility

Barrier affecting people with disabilities

  

autorelease: pending

  

autorelease: tagged

  

bug

Something isn't working

  

dependencies

Pull requests that update a dependency file

  

documentation

Improvements or additions to documentation

  

duplicate

This issue or pull request already exists

  

enhancement

New feature or request

  

github_actions

Pull requests that update GitHub Actions code

  

good first issue

Good for newcomers

  

help wanted

Extra attention is needed

  

invalid

This doesn't seem right

  

needs measurements

Waiting for before/after measurements

  

question

Further information is requested

  

testing wanted

Wanted: a test on other hardware (posts a test request in #test-requests)

  

wontfix

This will not be worked on

No labels

accessibility

autorelease: pending

autorelease: tagged

bug

dependencies

documentation

duplicate

enhancement

github_actions

good first issue

help wanted

invalid

needs measurements

question

testing wanted

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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/Longshot!5

No description provided.