You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
git allows to sign commits and tags¹ using the flags -S and -s respectively.
It could be great if git-graph could sign¹ every action it is performed in its GUI.
Additional context (optional)
vscode already has a setting to enable this:
With this option enabled, every action done using the built-in GUI is signed. But, git-graph does not support this, so mixing actions between both (like making commits in vscode and merging branches in git-graph) produce a mix of signed and unsigned commits.
I suggest to check if that option is enabled and sign accordingly.
¹ if the user has previously configured their keys.
The text was updated successfully, but these errors were encountered:
I created two new extension settings (git-graph.repository.sign.commits and git-graph.repository.sign.tags) to control commit and tag signing respectively, instead of using the existing Visual Studio Code setting git.enableCommitSigning. This is because git.enableCommitSigning is specifically for signing commits, so some users may have found it misleading if it also meant Git Graph started signing tags. Although I could have just created a new setting for signing tags, and used git.enableCommitSigning for signing commits, this would have meant users would have to enable two completely separated settings in the Visual Studio Code Settings Editor. I think creating two new settings (grouped together) was ultimately the best solution, even though it would have been nice to share the same setting as the Visual Studio Code Git Extension.
If you'd like to use it before the next release, you can download v1.28.0-beta.0, and install it following the instructions provided here.
Describe the feature that you'd like
git
allows to sign commits and tags¹ using the flags-S
and-s
respectively.It could be great if git-graph could sign¹ every action it is performed in its GUI.
Additional context (optional)
vscode already has a setting to enable this:
With this option enabled, every action done using the built-in GUI is signed. But, git-graph does not support this, so mixing actions between both (like making commits in vscode and merging branches in git-graph) produce a mix of signed and unsigned commits.
I suggest to check if that option is enabled and sign accordingly.
¹ if the user has previously configured their keys.
The text was updated successfully, but these errors were encountered: