You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One popular branching strategy, when dealing with maintenance/patch releases, is to late-cut branches. That is, you end up with something like:
- main
- releases/v1
- releases/v1.4
- releases/v2
- etc
There may or may not be a floating major/minor release branch, depending on whether there are any bug fixes for any particular released version.
The problem is that currently refFilterForPush would require listing all such branches explicitly, meaning modifications to CI scripts for each release.
Instead, it would be nice if refFilterForPush supported pattern matching/globbing:
Would you be open to an opt-in refFilterForPushMode: glob, with exact as the default? That would let refs/heads/releases/v* match refs/heads/releases/v1 and refs/heads/releases/v1.4 without changing what existing workflows push. For a first pass, I'd match the full ref case-sensitively and have * stay within one path segment, so it wouldn't match refs/heads/releases/V1 or refs/heads/releases/v1/extra. The event filter and push: always/never would stay unchanged.
Would you prefer the equivalent opt-in for Azure DevOps' sourceBranchFilterForPush in the same PR, or start with GitHub Actions?
Activity
sinbumu commentedon Nov 21, 2026
Would you be open to an opt-in
refFilterForPushMode: glob, withexactas the default? That would letrefs/heads/releases/v*matchrefs/heads/releases/v1andrefs/heads/releases/v1.4without changing what existing workflows push. For a first pass, I'd match the full ref case-sensitively and have*stay within one path segment, so it wouldn't matchrefs/heads/releases/V1orrefs/heads/releases/v1/extra. The event filter andpush: always/neverwould stay unchanged.Would you prefer the equivalent opt-in for Azure DevOps'
sourceBranchFilterForPushin the same PR, or start with GitHub Actions?