ci(tests): run on PRs targeting epic/** integration branches - #276
Merged
Conversation
Long-lived feature work now merges through an epic/<feature> integration branch before landing on main. Add epic/** to the pull_request and push branch filters so PRs targeting an epic branch — and pushes to the epic branch itself — run the full suite instead of nothing.
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.
What
Adds
epic/**to thepull_requestandpushbranch filters intests.yml.Why
Upcoming multi-PR feature work will use a long-lived integration branch (
epic/<feature>) that individual PRs merge into, before the whole thing lands onmainin one final PR.Today CI triggers only on
main, andpull_request.branchesfilters on the PR's base branch — so a PR targeting anepic/*branch runs no checks. This change makes:epic → mainPR.The final
epic → mainPR is already covered by the existingmainrule.Notes
tests.ymlis touched. Release workflows (release.yml,desktop-release.yml,docker-publish.yml) intentionally stay onmain/tags so nothing ships from an epic branch.**(not*) so nested names likeepic/agent-revampand deeper match.Convention
epic/<feature>(e.g.epic/agent-revamp)type/<feature>-<slice>(e.g.feat/agent-revamp-streaming), based on and merged into the epic branch.🤖 Generated with Claude Code