Install Evergreen workflow#357
Merged
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
.github/workflows/evergreen.mdwith a fresh Evergreen Agentic Workflow install..github/workflows/shared/skills/..github/workflows/shared/evergreen/..github/workflows/evergreen.lock.ymlwithgh aw compile evergreen.Install decisions
evergreen.evergreen-ready,evergreen-blocked,evergreen-human-needed,evergreen-exhausted.maininto PR branches only through labeled PR branch repair work.Test & Lint,Playground E2E (Playwright),Validate Python Examples,Build;OpenEvolve benchmarkonly for relevant Autoloop evolve PRs.README.mdor.autoloop/programs/**; protect workflow/config files unless a human confirms.Verification
gh aw compile(succeeded; existing unrelated workflow warnings were emitted)gh aw compile evergreen(succeeded with 0 errors, 0 warnings)apm compileattempted, but this repo is not an APM project because noapm.ymlexists.git diff --checkRepo setup applied
Created labels:
evergreen,evergreen-ready,evergreen-blocked,evergreen-human-needed,evergreen-exhausted.No new secrets/settings were needed;
COPILOT_GITHUB_TOKENandGH_AW_CI_TRIGGER_TOKENalready exist.Note: the requested upstream
INSTALL.mdpath was not present ingithubnext/evergreenat install time; I followed the current upstream README/docs install notes and v1 workflow design instead.