Same here. At least for me, the hard part is figuring out how to do it.
Comment on Always commit
Zeth0s@lemmy.world 1 year agoI would lose max 3 hrs of work that I already know how to re do. I can live with that. I don’t want to publish unfinished work. There is always the chance someone might need the branch.
explodicle@local106.com 1 year ago
Michal@programming.dev 1 year ago
Why not? Do you push directly to master?
Zeth0s@lemmy.world 1 year ago
Because someone else might need to work on my branches. And I don’t want garbage in my history. There are case I might not be able to squash merge, so all my history will be in the project history. I want each commit to be clean. It is not a lot of effort, and force me to increase code quality, because I review my code more often.
Rules for all projects I manage: never rebase published branch and always publish clean code (even implementation is unfinished).
From experience following these simple rules make the whole project management easier and more effective