Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to resolve issue while attempting to pull


Can anybody help me to check this issue when try to pull. Thank you so much!

git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks fetch --no-tags origin

git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks pull origin feature/kwa-417
* branch feature/k-417 -> FETCH_HEAD

fatal: Not possible to fast-forward, aborting.
Completed with errors, see above.

1 answer

0 votes
Erez Maadani
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 21, 2022

Hey @Tony Ho _Vinova_ 

git pull is actually git fetch and git merge.

As you can see above, git fetch is working fine so the failing step is the merge from your local copy of your remote branch into your local branch.

The error you get is that it's not possible to do fast-forward, which probably means that you have local changes/commits which were not pushed to the remote branch. The command `git status` will help you to get more info.

If you need to keep your local changes, the most common option to resolve this kind of issues, is to use explicit merge strategy, and not the only-fast-forward strategy. Have a look here: for more info.

Another option would be to:

  • Move your local changes/commit to a different branch.
  • Reset your local branch back to the last common commit with your remote branch
  • Merge the changes from your remote branch
  • Re-apply the changes from the new branch you created on your local branch. 


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events