Split Evergreen PR trigger from agent workflow#358
Merged
Conversation
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.
Summary
pull_requestactivation from the agentic Evergreen workflow.workflow_callinputs to.github/workflows/evergreen.mdand recompiles.github/workflows/evergreen.lock.yml..github/workflows/evergreen-trigger.ymlusingpull_request_targetto gate labeled PR events before calling the reusable Evergreen lockfile.pr_numberandhead_shainto the callable workflow; Evergreen re-fetches the PR and no-ops if the head SHA has changed.Why
The prior
pull_requesttrigger could hit gh-aw confused-deputy protection on bot-authored PRs: the run appeared successful, but pre-activation skipped the agent. This keeps fast PR-event reaction without handing raw PR-event context directly to the agentic workflow.Verification
gh aw compilesucceeded; existing unrelated Autoloop/CI Doctor warnings were emitted.gh aw compile evergreensucceeded with 0 errors and 0 warnings.actionlint .github/workflows/evergreen-trigger.ymlgit diff --checkapm compileattempted; repo is not an APM project because noapm.ymlexists.Note: I scoped the commit to Evergreen files and did not include unrelated lockfile churn from the full
gh aw compilerun.