Let a bot-test label force the test-data flow on any PR - #432
Merged
Conversation
A maintainer-applied bot-test label makes the bot treat the author as external, so the comment and label flow can be exercised end to end without a fork account. The workflow also fires on labeled. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Adds a maintainer-only test hook to the test-data bot: a
bot-testlabel makes it treat the author as external, so the full comment and label flow can be exercised without a fork account. Labeling needs triage access, so contributors cannot self-trigger. The workflow also fires onlabeled. The skip decision moves into a pure helper with unit tests.