Make sure you then select the tab that says "Changes". This super-handy, always-hidden little feature, however, is still there.įirst, select your repository in the far-left dropdown in the black area. ![]() So if you're running Github Desktop v1 then your UI is going to look a little different. It's now called Github Desktop and the version numbers have started back at v1.0.0. In keeping up with the times, Github for Windows has had a huge makeover, so here's a new answer. (How one would know to right-click is beyond me.) If you right-click in the space next to "Files to commit" you'll have an option to "Discard all changes." Click that and presto, all your changes are wiped out and your local files will be back to where they were the last time you made a commit. ![]() If you right-click on any file you'll have an option to "Discard changes". Super easy - Select your repository in the leftmost column and then click "Uncommitted Changes" in the 2nd column to display your changed files at the right. Obviously, you may enter other git commands here as well. From there you can type git reset -hard to revert files modified since the last commit and then git clean -fd to remove all files added since the last commit. The shell should open and be in the directory of your repository. There are two options - the first is easy and the second is super-easy:Įasy - Select your repository in the leftmost column then click the gear icon in the upper right and choose "Open in Git Shell". (When you select "Uncommitted changes" in the 2nd column, the "Revert" link is not there. If you select one of those commits, in the right column at the top you'll see "Revert" which says, when you mouse over, "Create a new commit that reverts the changes in this commit." I don't think this is what you want to do since you don't want to revert the changes in that commit but rather revert the changes that haven't been committed yet. ![]() I'm keeping an eye out for a repeat of the issue to see if I can get more accurate detail, hopefully I can find something that helps.When you open GitHub for Windows v2.0 (ancestor of GitHub Desktop) and select your repository in the leftmost column, you'll see all your previous commits in the 2nd column from the left. Given the steps I detailed, maybe it's some form of desync in the code? Or it is receiving it and just.not acting on it. Which could mean anything from an internal version counter being set incorrectly to it simply not receiving data from origin about the state of the repository. ![]() This would of course require verifying that origin remote and upstream are in sync, yes? If they -are- then that means that the program itself is not fetching data from either. Github desktop is not properly fetching origin remote state, for one reason or another. Trying to think this through from a troubleshooting standpoint: Some things which have changed since maybe around the same time (i'm not reliable for info on this, due to memory problems), the upstream has some special things (idk the term) which check every pull request. Well, in that case i'll try to provide more detail, see if we can't find some common causes?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |