Auto-label dependabot and viam-overwatch PRs safe to test - #909
Merged
Ale Paredes (ale7714) merged 1 commit intoSep 24, 2026
Merged
Conversation
Both bots push same-repo branches but are not org members, so the membership call threw for them, the step failed, and someone had to add the label by hand. The label is applied with PR_TOKEN because a GITHUB_TOKEN label event does not start pullrequest.yml, so a labeled bot PR would otherwise not test until its next push. The bot path never applies to fork heads, so a fork cannot use a bot login to skip the check. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Ale Paredes (ale7714)
deleted the
fix/pr-labeler-trust-dependabot-overwatch
branch
September 24, 2026 19:55
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dependabot and viam-overwatch push same-repo branches but are not org members. The membership call throws for a non-member, so the labeler step failed on every bot push and someone added
safe to testby hand (see #884). The script now mirrors rdk's labeler: a trusted-bot list for same-repo heads, a fail-closed membership check, and a non-fatal label removal.The label is applied with the org
PR_TOKENinstead ofGITHUB_TOKEN. A label added withGITHUB_TOKENdoes not fire thelabeledtrigger in pullrequest.yml, so a bot PR would sit labeled but untested until its next push. rdk, goutils, docs and slam-cloud-session already label withPR_TOKEN.A fork PR never takes the bot path, so a bot login cannot skip the membership check from outside. Same shape as viamrobotics/rdk#6536.
🤖 Generated with Claude Code