jira-importer commented on issue #661: URL: https://github.com/apache/maven-scm/issues/661#issuecomment-2964611871
**[Jonathan K. Schneider](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jschneider)** commented Okay, just my opinion: I run into that problem, too. I really **hate** that push. I prefer to do that manually after everything worked as expected. And sometimes I prefer to adjust that commits too (multi module projects). At the moment I end up deleting tags from origin and often doing a "git push -f" if something failed (e.g. site generation)... That does not seem to be the best solution... Others here have also said, that they prefer **not** being forced to push to origin. So there are the user stories you asked for. So the solution seems to be very simple: - Clone from ${basedir} instead of origin during the release. That might solve some other issues too (performance, traffic, merge conflicts when origin has changed in between). - Make the push optional! That allows everybody to follow his preferred work flow. While I strongly believe that **distributed** VCS never should push automatically, I accept that some people out there are still "brainwashed" by the use of a centralized VCS for decades. So for me it is ok, to push by default. But please offer an option to skip that... By the way: Thanks for your work... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
