Open daily from 9:00 to 20:00Get in touch
NewWe collected answers to the questions people ask most oftenOpen the section →
🍪 Cookies and personal data

We use cookies to keep the site working and make it more convenient, and we process anonymised data about your visit. The details are in our privacy policy.

Pushing: conflicts and what to do when it is rejected

31.08.2026 ~1 min read
Pushing: conflicts and what to do when it is rejected

A commit lives on your machine until it is pushed. Pushing is a separate action, and it can be rejected: that means the shared history has gained something you do not have.

git push origin master   push
git pull --rebase        take theirs and put yours on top
git push origin master   try again

A conflict is not a breakage but a message saying "two people edited the same place, decide which is right". You open the conflicted file, keep what is needed, remove the markers and make an ordinary commit. The more often you pull, the more rarely this happens.

More lessons in this course

Discussion

0

Only signed-in visitors can comment. Sign in to write.

Nobody has spoken up yet. Be the first.

Still have questions?We reply within one business day — write to us whichever way suits you.
Contact us