I 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 too much unfinished/unpolished work. There is always the chance someone might need the branch.

Even if drafts under development, I like to publish something that reaches the standard of my "best" me, not my "Friday evening" me

[–] Michal@programming.dev 2 points 1 year ago (1 children)

Why not? Do you push directly to master?

[–] Zeth0s@lemmy.world 0 points 1 year ago* (last edited 1 year ago)

Because someone else might need to work on something on or from my branches. And I don't want garbage in my history. There are cases 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 forces me to increase code quality, because I review my code more often.

Rules for all projects I manage: never rebase published branches and always publish clean code (even implementation is unfinished).

From experience following these simple rules make the whole project management easier and more effective

[–] explodicle@local106.com 1 points 1 year ago

Same here. At least for me, the hard part is figuring out how to do it.