commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Barnhill <>
Subject [git] please avoid force pushes
Date Thu, 13 Jun 2019 17:29:30 GMT
Apologies if everyone knows this but...

There has been some force pushing in the git repos lately. Unfortunately
there are a lot of Stack Overflow answers that will tell the user to solve
a complex commit situation by force pushing. These answers are just
*wrong*. By the nature of our code it is being used by more than one
pseron, and therefore force pushing should never happen. There is always a
better way.

If your commit situation gets complex, consider starting a new branch. You
can then push it without conflicts, and you can probably PR over your
master or develop branch without rewriting any history. If that still
doesn't solve your problem, you can ask here or DM me on the ASF Slack.

I am only miiltant on this because I once created pandemonium early in my
new job by force pushing after Stack Overflow suggested it. Fortunately we
recovered and I was not fired. Just say no to push -f. :)

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message