← Quiz: GitHub: all 10 questions
Quiz: GitHub · Question 5 of 10
Why is git push --force dangerous on a shared branch?
Why is git push --force dangerous on a shared branch?
- A.It's slow
- B.It can overwrite commits that teammates already pushed
- C.It deletes your local repository
- D.It creates a new branch
Answer & explanation
Correct answer: It can overwrite commits that teammates already pushed
Force-pushing replaces remote history with yours.
Can you get the rest right without peeking?
Take the timed Quiz: GitHub quiz free. Pass it to earn XP and count towards your certificate.
Start the quiz →