Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,457,618
Community Members
 
Community Events
176
Community Groups

Can I delete/tidy up old FETCH_HEAD files?

Peter Hitchmough
Peter Hitchmough Apr 17, 2018

My local repository is in a One Drive local folder. it looks like there was a glitch and I have ended up with twp versions of file .git/FETCH_HEAD-<pc-name>-94. In fact there are several files, ending in -93, -92, ... -4, -3, -2.

As I understand it these FETCH_HEAD files are short-lived files representing the fetch status from my remote repository (I only have origin).

  • Can I delete all these old .git/FETCH_HEAD files?
  • Is there a git or Sourcetree command to reconcile my local and remote repos?
Answer
Watch
Like dr_eck likes this
3280 views

2 answers

0 votes
andrewstalker
andrewstalker May 28, 2021

Yes you can delete FETCH_HEAD files. They are only temporary. 

In their absence, GIT will have to recreate the file and reassert the fetch status of the files in the repo. 

Reply
0 votes
minnsey
minnsey Atlassian Team Apr 17, 2018

Hi

Personally when git goes bad, if possible I tend to cut my loses and backup that copy and re-clone.

Other than that you could try git fsck to see if that offers any solutions https://git-scm.com/docs/git-fsck

Reply

Suggest an answer

Log in or Sign up to answer
Sourcetree
Sourcetree
TAGS

Atlassian Community Events

See all events