Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"git push -f" without due diligence #93

Open
lassevk opened this issue Aug 28, 2018 · 2 comments
Open

"git push -f" without due diligence #93

lassevk opened this issue Aug 28, 2018 · 2 comments

Comments

@lassevk
Copy link

lassevk commented Aug 28, 2018

I believe "git push -f" is bad advice unless enough due diligence has been done to verify that this won't cause bigger problems. I downvote answers that jump to this command without such work.

This is a pet peeve of mine, people grab "git push -f" far too quickly to solve any number of problems. Yes, in most cases it will involve force push, but only after verifying that this won't cause bigger problems.

I've seen numerous questions like "I used git push -f --mirror and now I lost branches and commit", "I used git push -f and now my colleague is mad at me" and similar.

"git push -f" requires more work before this advice can be given and I for one downvote answers that just jump to this command before verifying anything of the sorts.

@WillSullivan
Copy link
Owner

I dunno... this is a bit... specific. Let's see if other people are interested in adding a page for this issue. I have no idea how wide spread it is.

@sonic1981
Copy link

The correct response to this kind of thing is to point the person suggesting this to a question on SO that explains why they shouldn't do this or if it's a question, vote to close as a duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants