Just pick the hash you want to go back to and in your clone do: git reset –hard hash# git push -f origin branch where branch is the name of the branch you want to push. Voilà. Be carefully with the force push. You may want to copy your working directory until you are familiar … Read more
Just use git stash pop or git stash apply. As long as the stashed changes do not conflict with what you pulled or edited, it will just work, if not you get some merge conflicts that you can resolve like when you do a merge or rebase.
From testing: GETing /users/someusername/repos doesn’t show private repos (even if it’s the user whose oauth access token you’re using). GETing /user/repos show private repos. This isn’t documented in the GitHub API docs at present, I just found out via testing. Thanks to @ivanzuzak for suggesting to look at the endpoint.
First, you should always make your PR form a branch, not from master. master is for mirroring upstream/master, with ‘upstream‘ being the name of the original repository that you forked. In your case, make sure that: make sure that upstream exists (git remote -v), make a branch in order to reference your current patches, and … Read more
Like Nasreddine says, it’s because your key is encrypted with a passphrase to prevent others from reading it. The most convenient way of using passphrased keys is by using ssh-agent to start an authentication agent (which runs in the background): $ eval “$(ssh-agent)” Agent pid 44304 …and then using ssh-add to register your key with … Read more
In my case the issue was solved by invalidating cache and restarting IDE. Simply go to Files -> Invalidate Caches -> Invalidate and Restart.
The old post you refer to is “Syntax Highlighted Diffs”, Dec. 2014 However, nothing in the current GFM (GitHub Flavored Markdown) suggests this particular combination (of diff and syntax highlighting) is currently supported.
GitHub keeps track of forks made through their interface and assumes pull requests will be for that original repository. You need to tell GitHub that your copy is not a fork but rather a regular repository that just happens to have identical history. Sadly, GitHub doesn’t offer a good way to just uncheck the fork … Read more