This is from the automation today, right? <https:/...
# automations-debug
c
m
yes
c
@fresh-machine-37269 Find this automation in your environment and make it skip release PRs, like the above linked PR. It’s needed only for the other PRs, and it’s noise in these. You can find other workflows working on release PRs to take as example of a simple way to recognize them.
πŸ‘€ 1
f
πŸ€– On it! View progress here: oss-agent-canvas.ngrok.dev/conversations/…
βœ… Done! Found it. The "HUMAN: section needs 20 characters" comment on PR #462 came from the GitHub PR Reviewer (multi-repo) automation (covers extensions, OpenHands, and software-agent-sdk), which posts as
all-hands-bot
and polls every 2 min. I made it skip release PRs entirely. Following the same pattern the
release-ready
reusable workflow in
OpenHands/release-actions
uses, it now recognizes release-please PRs by their
autorelease:
label prefix (PR #462 carries
autorelease: pending
) and skips them before any of the gates run β€” so no HUMAN-section comment, no CI-gate comment, no Slack ping, and no AI review on release PRs. Other PRs keep getting the full treatment as before. The change is deployed (new tarball uploaded and pointed at via the automation API) and verified: the automation runs cleanly with it, and the deployed code in the run sandbox contains the new
_is_release_pr()
check. PR #462's labels are correctly detected as a release PR. One note: during testing the automation kept reporting "could not reach GitHub to verify token (403)" and skipping all repos β€” that's the
GITHUB_TOKEN
on this VM being rate-limited (I hit the same 403s while investigating), not related to the change. It retries next poll, so once the token recovers, release PRs will be skipped and everything else resumes normally.
c
Aww. πŸ˜… It changed the automation, not the extensions/ repo automation
Which is kinda correct too, to test it live after all. πŸ«