I've got a fix ready for this, I just wanted to ensure we have a record of this being a bug that we can refer back to. The PR branch is checked out and the stash on the previous branch is overwritten with a newly created stash containing your uncommitted changes. GitHub Desktop should show a confirmation prompt like the one below it works like a stack where changes are pushed and popped off the stash. This is commonly where I use the git stash. For example, you may want to change branches. If you use GitHub Desktop to switch branches while you have saved, but not committed, changes, GitHub Desktop will prompt you to stash the changes or bring them to the other branch. The Git Stash is a holding area for in progress changes that you want to preserve but need keep out of the way temporarily. After you stash changes on a branch, you can safely change branches or make other changes to your current branch. Attempt to check out a pull request (note: not a branch, there's different logic involved here) If you use GitHub Desktop to stash changes, all unsaved changes will be stashed.Ensure you've selected the "Always stash and leave my changes on the current branch" option in preferences.Ensure you have uncommitted changes in your working directory.You can select one commit or select multiple commits using Ctrl or Shift. If you use GitHub Desktop to stash changes, all unsaved changes will be stashed. When attempting to publish a commit, it will ask for authentication showing local server name in the box and requesting a username/password but nothing happens after entering this information. You can only stash one set of changes at a time with GitHub Desktop. Select the commits to squash and drop them on the commit you want to combine them with. GitHub for Windows GUI Client is being used to manage Git repositories and then integrate with Stash. Ensure your current branch has a stash associated with it. In the list of branches, select the branch that has the commits that you want to squash.OS-independent Steps to reproduce the behavior I believe this has been true since #8813 which shipped in 2.3.0. When checking out a branch using the pull request list or by following a "Checkout in Desktop" link on while having the "Always stash and leave my changes on the current branch" option selected in preferences (under Advanced) GitHub Desktop fails to prompt the user for confirmation before overwriting their existing stash.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |