Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running stg commit should GPG sign commits #370

Open
Techcable opened this issue Sep 11, 2023 · 2 comments
Open

Running stg commit should GPG sign commits #370

Techcable opened this issue Sep 11, 2023 · 2 comments

Comments

@Techcable
Copy link

In my opinion, GPG signing temporary stack metadata is pretty useless, so I have stg.gpgsign = false.

However, I have commit.gpgsign = true. I assume that running stg commit would respect the second option and generate signed commits.

However, it does not. The resulting commits continue to be unsigned.

Techcable added a commit to Techcable/dotfiles that referenced this issue Sep 11, 2023
Avoid the 'hacky fixup' script, just assume behavior is correct.

See issue stacked-git/stgit#370

Right now commits aren't signed when using 'stg commit'
@Techcable
Copy link
Author

One workaround is git rebase --force-rebase

@jpgrayson
Copy link
Collaborator

Setting commit.gpgsign = true and stg.gpgsign = false should result in regular patch commits being signed. I typically run with this setup and it works for me. I'm sorry it isn't working as it is supposed to for you.

A little more information about the StGit and Git versions where you are seeing this would be helpful. Also, where the configuration is in your environment, i.e. are these options being set globally? Locally? Or a combination of both?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants