Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Reset master to commit after pushing commits to the origin/master Edited

Screen Shot 2018-01-10 at 11.03.10.png




As you can see in the screenshot, my local master is 2 commits behind on the origin.  

But I deliberately executed 'Reset master to this commit' and I want the origin/master to follow. So how can I continue with my local master and push to the origin? 

When I make a commit on my local master I get this situation:

Screen Shot 2018-01-10 at 11.14.49.pngI obviously don't want to pull but I can't push neither (getting a message that I have to pull first).  

If I pull I go back to the commits I didn't want.  How can I go on from the 'Last Commit before Upgrading SIS' (locally and remote)?

2 answers

1 accepted



After a lot of trying I'm back to my original situation(see screenshot one).

I tried to reverse the two commits 'sis commti' and 'SIS Clean up' but I'm only able to reverse one and then get the message:

Screen Shot 2018-01-10 at 13.37.53.png 


How to solve this situation?



 In the terminal I want to try the following:

git checkout master
git reset --hard e3f1e37
git push --force origin master
# Then to prove it (it won't print any diff)
git diff master..origin/master

But after

git checkout master

I get the following

fatal: Unable to create '~/.git/index.lock': File exists.

Another git process seems to be running in this repository, e.g.
an editor opened by 'git commit'. Please make sure all processes
are terminated then try again. If it still fails, a git process
may have crashed in this repository earlier:
remove the file manually to continue. 

Does this has anything to do with the Bitbucket storage layer incident? 

Or what am I missing?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Sourcetree

Tip from the team: configure your repos for hosting goodness!

Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...

3,270 views 4 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you