• 0 Posts
  • 265 Comments
Joined 11 months ago
cake
Cake day: August 8th, 2023

help-circle

















  • It depends on your intent. If you’re doing it to keep history clean and linear in the long term, it’s a huge waste of time as it gets splatted into a single squashed merge commit. It also makes it difficult for reviewers to rereview your changes as GitHub/Lab can’t calculate the diff because you keep moving the goalposts with force pushes.

    If you’re doing it for cleanliness on your local branch then I guess that’s fine, but I find it anti-social in a multi participant repo.



  • The original comment I replied to made a definition of evolutionary success and I made a counter-definition. I’m not sure what conversation that you’re referring to before that. There was only one other comment above it in the chain and it had little do with defining the evolutionary success of chickens or what that might entail.

    If you’re perceiving an agenda where there is none while also not understanding the point being made then, not to be rude, but thats a comprehension issue.

    It’s possible I’m explaining it poorly, but I’ve run out of ways to approach this so I can’t offer you anything more.