Repository navigation
bot-runs: Find the apply job under any reusable-workflow nesting - #186
Merged
Merged
Conversation
bot-runs read an agentic-job run's application status from a job named exactly "run / apply". The dispatch workflow now runs through a wrapper and the job is "run / apply / apply" (it was "apply / apply" before that), so the status has read "missing" for some time. Match on the last " / " segment being "apply" instead, which also excludes the sibling "conclude" job whatever the nesting. Generated-by: AI
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.
The apply job of an agentic-job run is now
run / apply / apply, so bot-runs, which looked for exactlyrun / apply, has reported the application asmissing. Match any job whose last/segment isapplyinstead (so notconclude), with a data-driven test.Generated-by: https://github.com/cgwalters/#llms