Its useful if a repository has become badly damaged. It is also a good idea to run git annex fsck -fast after man git-annex-repair (1): This can repair many of the problems with git repositories that git fsck detects, but does not itself fix. This command does not try to clean up either the Note that fsck may stillĬomplain about objects referenced by the reflog, or the stash, if they were Note that the -force option never touches tags, even if theyĪre no longer usable due to missing data.Īfter running this command, you will probably want to run gitįsck to verify it fixed the repository. git-annex allows managing files with git, without checking the file contents into git.
This is useful to run manually when you have been moving the symlinks. force option, since that rewrites history and throws out missingĭata. Fixes up symlinks that have become broken to again point to annexed content. If that is not sufficient to fully recover the repository, it canĪlso reset branches back to commits before the corruption happened, deleteīranches that are no longer available due to the lost data, and remove any It works by deleting any corrupt objects from the git repository,Īnd retrieving all missing objects it can from the remotes of the Not use git-annex at all when used in a repository using git-annex, it doesĪdditional repairs of the git-annex branch. This command can actually be used inside git repositories that do Repository used by git-annex is on a removable drive that gets unplugged at Git fsck detects, but does not itself fix. This can repair many of the problems with git repositories that Git-annex-repair - recover broken git repository SYNOPSIS ¶
0 kommentar(er)
