Last active
April 13, 2018 17:06
-
-
Save aviaryan/5413425 to your computer and use it in GitHub Desktop.
Debug Error - GitHub for Windows, -->
debug the state of this repo - Easy Fix
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| By Avi Aryan | |
| This Text explains how to get around with "debug the state of this repo" Error. | |
| This text does not uses Cmd and Powershell, so it can be followed by a basic user. | |
| If you face the above Error in GitHub for Windows, then ------ | |
| * First Go to your local repo i.e. the repo's local folder. | |
| * Show Hidden Files via the Folder Options. | |
| * You will see a ".git" named folder in your local repo as soon as hidden files are set to be seen. | |
| * Delete That. | |
| * Now open Github for Windows. | |
| * Now, if you click on that repo in Local Tab, you should get an Error that repo cant be found. | |
| * | |
| * There it is, click on Re-Clone Repository button. | |
| * | |
| * The Repo will be downloaded again, with all commits and saved by default in -- My Documents/GitHib/<RepoName> | |
| Enjoy! |
Sometimes when using git pull, it gives an error: "Permission denied". To fix this, make sure that no other processes are using those files (e.g. any watch compilers, text editors, web servers...)
Check https://github.com/settings/emails if your email is set to private. Revert to public if it is.
This showed up when apparently I had a file that was too large in my commit. When I opened up powershell and used git push, it revealed the source of the error. Though I imagine the github desktop app throws this message for a variety of reason
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I had the same issue as the commenters... git status shows no errors, I can update via git pull, but I can't use the desktop app... Something about SSH agent failing to load... Had to reinstall and reclone the git....