We tested this with Gpg4win(Gpg4win vanilla is sufficient and with version 2.2.x it is also compatible to GPG 1.4 key files). This can be done be setting the configuration variable gpg.program (e.g., C:/Program Files (x86)/GNU/GnuPG/pub/gpg.exe). GPG >= 2 comes with an agent like pageant and, thus.also works with passphrase protected keys, however, you might need to configure git to use the right gpg.exe. When using GPG 1.4 (which is shipped with Git for Windows) this requires a key without a passphrase. This requires GPG and also the configuration variable user.signingkey to be set (see the section called “Git Config” and the section called “git-config(1)”). The third state indicates, that neither -track nor -no-track is passed to git on OK - see tosetupmerge configuration variable ( the section called “git-config(1)”) and -track parameter documentation for the section called “git-branch(1)”.Ĭheck Sign to create a GPG signed tag. If it is checked -track is passed to git on OK, if it is unchecked -no-track is passed to git on OK. If it does, those changes will be merged into the branch working tree when you switch. But if you do that, first make sure that your working tree does not contain modifications. If you want your working tree to be switched to the newly created branch automatically, use the Switch to new branch/tag checkbox. You also can input commit hash, or friendly commit name, such as HEAD~4. Saved working directory and index state WIP on master: 4402b8c testingĭropped refs/ (db1b9a3391a82d86c9fdd26dab095ba9b820e35b) No changes added to commit (use "git add" and/or "git commit -a")
" to discard changes in working directory) Nothing to commit (working directory clean) I supposed git stash & git stash branch new_branch would simply accomplish that but this is what I get: This always happens to me and I have no idea how to switch to another branch and take all these uncommitted changes with me leaving the master branch clean.
After a few minutes, I realize it was not so simple and it should have been better to work into a new branch. Context: I'm working on master adding a simple feature.
0 kommentar(er)
