You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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).
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.