4 ms·
Doesn't that requires a force push? Force pushes are acceptable for private repositories with a single user, but typically not in larger projects. Just revoke
by danieldk 10y ago
Doesn't that requires a force push? Force pushes are acceptable for private repositories with a single user, but typically not in larger projects.
Just revoke the password/secret/whatever.
- adrianN 10y agoOr do both? Better safe than sorry.
- jomkr 10y agoIt's better to just revoke and not re-write git history in a public repository. Re-writing history is pointless after the credentials are revoked, and causes a headache to others using your repository.
- majewsky 10y agoI find force pushes acceptable for topic branches of public repos. In fact, I use them a lot to leave behind clean history. Same as with squash merges, which technically also lose history.
- prodigal_erik 10y agoIt's better to push a similar name and let people decide if and when to rebase --onto the new upstream. Squash merges are just bad. They destroy all the info that makes git handle branching and conflicts better than svn.