Add head_branches and ignore_head_branches to filter PRs based on head branch name
#185
Conversation
This file contains 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
ctreatma
changed the title
head_branch_filter to filter PRs based on head branch namehead_branches and `ignore_head_branches to filter PRs based on head branch name
ctreatma
changed the title
head_branches and `ignore_head_branches to filter PRs based on head branch namehead_branches and ignore_head_branches to filter PRs based on head branch name
ctreatma
force-pushed
the
feature/head_branch_filter
branch
from
b273669 to
889c714
Compare
ctreatma
force-pushed
the
feature/head_branch_filter
branch
from
889c714 to
a732c70
Compare
|
Any thoughts on this? We've been using it for a while now to allow us to define separate workflows for release branches and feature development branches; using the |
ctreatma
force-pushed
the
feature/head_branch_filter
branch
from
a732c70 to
16a3a2a
Compare
ctreatma
force-pushed
the
feature/head_branch_filter
branch
from
16a3a2a to
f3c6af6
Compare
ctreatma
force-pushed
the
feature/head_branch_filter
branch
from
f3c6af6 to
b7e1272
Compare
For some workflows, it can be useful to treat pull requests differently depending on the name of the head branch for the pull request. For example, a team following scaled trunk-based development might use the `release/*` naming convention for release branches, and may have different build/deploy processes for those release branches. This adds `head_branches` and `ignore_head_branches` settings to this resource, specified as a glob pattern to align with similar filters on the Concourse git resource, so that teams can run different jobs based on the head branch of a PR. See: https://trunkbaseddevelopment.com/#scaled-trunk-based-development
ctreatma
force-pushed
the
feature/head_branch_filter
branch
from
b7e1272 to
30a2276
Compare
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.
For some workflows, it can be useful to treat pull requests differently
depending on the name of the head branch for the pull request.
For example, a team following scaled trunk-based development might use
the
release/*naming convention for release branches, and may havedifferent build/deploy processes for those release branches.
This adds a
head_branchesoption and anignore_head_branchesoptionto this resource, specified as a glob pattern to align with similar filters on the
Concourse git resource, as well as with the
pathsandignore_pathsoptions on this resource.
See: https://trunkbaseddevelopment.com/#scaled-trunk-based-development