Announcement

Collapse
No announcement yet.

How do you document development steps before deleting a branch?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • How do you document development steps before deleting a branch?

    As a new-ish Git user, I like to keep merged branches around to serve as a development artifact showing what code and steps solved an issue. Since it seems everyone prefers a clean branch list by deleting branches once that work is finished and committed, what do you use to preserve the development steps for each specific issue?

  • #2
    While I agree with you in terms of keeping the original set of commits - so that the "thinking" can be clearly seen - the vast majority of the users who use Git are of the opinion that each functional change should be squashed down into a single commit. So, what I try to do while squashing is to consider what the learnings were and embed them in the squashed commit comment (not the 1-liner, but the body below that after a blank line). It's the best that I can do given the prevailing winds. Of course, the same goes for actual code comments - they should be more about the "learnings" than what I normally find - and that's sad.

    Comment

    Working...
    X