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.
Purpose
I tend to follow a naming convention for branches, and when I work on big features that are split into different PRs, the beginning and the end of the branches contains the most significant context, i.e:
feat/<ticket_id>/<feature-name>-<feature-portion>
. In these cases I find useful seeing the beginning of the branch, and as I already know which feature I'm working on, I find more value by seeing the last part, as it usually refers to a smaller portion of the whole feature.Hopefully others also finds this useful.
Approach
Trim the branch from the inside out, so that
feat/COR-1032/supplier-billing-profile-invoice-upload
becomes
feat/COR-1032/…invoice-upload