this post was submitted on 19 Jul 2024
39 points (95.3% liked)
Git
2869 readers
7 users here now
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
Resources
Rules
- Follow programming.dev rules
- Be excellent to each other, no hostility towards users for any reason
- No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.
Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Often I commit because I have to jump to another branch, so I want to save my progress. This means I can be in the middle of something, so I write a trash message.
All those messages will disappear anyway after the merge request, because we use a squash policy. I can spend more time thinking of a more proper commit message when writing the merge request.
Isnt that what stash is for?
I don’t like stash for this purpose. What if I have to jump to a different branch a second time? Should I stash again?
It can be difficult to know which stash belongs to which branch. Nah, I rather just commit so I don’t need to bother with that confusion.
I agree that stash gets lost easier than a branch, but
you know, stash also has a message to it, and afaik it remembers what branch you were on when stashed
How about
WIP: <description of what you wanted but did not achieve yet>?git worktreecould become your new friend then :)I’m aware of that option. I haven’t bothered to learn it because this is a perfectly good system for me.