feat: trim branch from center#116
Merged
Merged
Conversation
rtalexk
force-pushed
the
feat/trim-branch-from-center
branch
from
June 9, 2024 00:39
551d1d8 to
a882b42
Compare
arl
reviewed
Jun 9, 2024
arl
left a comment
arl
left a comment
Owner
There was a problem hiding this comment.
Thank you for doing that, very helpful.
Can you please update the documentation in .gitmux.yml at project root? This file gets embedded in the binary at build time and serves as default config for gitmux -printcfg?
rtalexk
force-pushed
the
feat/trim-branch-from-center
branch
2 times, most recently
from
June 9, 2024 02:35
02a8952 to
cc84284
Compare
rtalexk
force-pushed
the
feat/trim-branch-from-center
branch
from
June 9, 2024 02:37
cc84284 to
45568dc
Compare
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
2 participants
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-uploadbecomes
feat/COR-1032/…invoice-upload