docs(agents): mark a PR ready after the update that finishes it, and measure every area a change touches #22
No reviewers
Labels
No labels
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Tooling!22
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/Tooling:docs/ready-after-update"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
AGENTS.mdtells agents to take a PR out of WIP once it is ready, but only at the moment it first gets there. A PR often becomes ready later, through its last measurement, fix-up or test run, and then sits in WIP where nobody reviews it.It also asks for a PR to be "measured" without saying what: PRs measure only the area they aim at, and miss the cost elsewhere (a compiler flag's build time, a cache's first-run load).
What changed
Two additions to
AGENTS.md, under the pull request rules:pr update, check again whether the PR is ready, and if it is,pr ready <n>then, rather than leaving a finished PR in WIP;The same notes go into Longshot's
docs/agent-pull-requests.mdin a companion PR (Longshot #1715).Testing
Docs only; nothing to run.
🤖 Generated with Claude Code
54d35b4235tod4b6bb9794docs(agents): check again whether a PR is ready after each updateto docs(agents): mark a PR ready after the update that finishes it, and measure every area a change touchesAdded a second note in the same commit: measure every area a change touches (game, build time and size, loading and caches, memory, the launcher and tools), not only the one it targets.