Allow wildcard matching for "branches" command #258
Merged
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.
This update adds branch name wildcard pattern matching to the "branches" command.
The use case is when a repository has many active branches and you just want to see branches matching a particular naming pattern.
The branch name wildcard patterns follow Unix filename pattern matching standards (from documentation for
fnmatch
):For a literal match, wrap the meta-characters in brackets. For example, '[?]' matches the character '?'.
Examples
branches
without wildcard:$ git branches develop (published) * gu-branches-wildcard (published) master (published)
branches
with wildcard: