For example, just copy-paste to a terminal. If you were not too slow, you need to make this request anyhow.
Append to the end of the copied line of code, this one: -H "Cookie=".Right-click on it and select "Copy as cURL" and save this text in some editor. On the same page, without reloading, open DevTools, Network panel.go to GitHub and create a new temporary branch which will be deleted for ever ( Chrome is preferable).(If the repo rquires two-factor auth, see the comments on this answer below.).If you want to restore it from GitHub website, you can use their API to get a list of repo-related events: Related: Easily recover deleted files that have been staged previously For each commit, sorted by date, you will have the hash, the commit message and will be able to display easily the commit diff. You can easily recover lost commits ( and also uncommitted staged files!) with via the menu Repository => Git maintenance => Recover lost objects. Access to reflog content for HEAD or another branch: In the menu Commands => Show reflogs.Display dangling commits in the revision grid (maybe the easiest): In the menu View => Show reflog references and you should now be able see the dangling commits present in the reflogs.Similarly to what you can do from the command line, you can take the commit hash from the reflog or from dangling commits: From the reflog
GITKRAKEN PUSH ALL BRANCHES HOW TO
Here are some examples showing how to analyze the found commitsĭisplay commit metadata (author, creation date and commit message): git cat-file -p 48540dfa438ad8e442b18e57a5a255c0ecad0560Īlso see diffs: git log -p 48540dfa438ad8e442b18e57a5a255c0ecad0560Ĭreate a branch on the found commit: git branch commit_rescued 48540dfa438ad8e442b18e57a5a255c0ecad0560 Then read the SHA of the missing commit and reset you branch to it.įrequent users may create the alias git rescue using git config -global alias.rescue '!git fsck -full -no-reflogs -unreachable -lost-found | grep commit | cut -d\ -f3 | xargs -n 1 git log -n 1 -pretty=oneline >. If your commits are not in your reflog (perhaps they were deleted by a 3rd party tool that doesn't write to the reflog), you may try this command first to create a file with all the dangling commits git fsck -full -no-reflogs -unreachable -lost-found | grep commit | cut -d\ -f3 | xargs -n 1 git log -n 1 -pretty=oneline >. if you had force pushed (though one should use git push -force-with-lease instead which prevents mistakes and is more recoverable). Perhaps something easier is to use the command git reflog name-of-my-branch if the commit was part of a specific and still existing branch. So, the first thing to try is to look at the reflog using the command git reflog (which displays the reflog for HEAD). Most of the time unreachable commits are in the reflog.
So you will have to find the commit hash and you will have 2 options explained just below:įinding commit hash with the command line When your commits are in the reflog Here is the command to create the new branch: git branch (Re)Creating the branch ONCE you've got the commit hash
0 kommentar(er)
