git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: fa <fa_ge-akarinnnnn@qq.com>
To: git <git@vger.kernel.org>
Subject: (Bug Report Form, zh-Hans) git-subtree not respecting commit.gpgSign
Date: Sat, 1 Nov 2025 20:54:58 +0800	[thread overview]
Message-ID: <tencent_D8444AABD439465DB4FA0D624A8E85A0220A@qq.com> (raw)

Dear git developers and maintainers,


I met some problems with git-subtree, it's little bothers me. Would you like to provide me some help? Here is the bug report form(localized).


感谢您填写 Git 错误报告!
请填写以下问卷,以帮助我们了解您的问题。


在错误发生之前,您做了什么?(重现问题的步骤)
I tried to push a subtree managed folder to a remote. With configured commit.gpgSign=true.


您期望发生什么?(预期行为)
All commits pushed to remote is signed by gpg.


实际发生了什么?(实际行为)
Pushed commits are not signed as expected. Or, commit.gpgSign is not respected by git-subtree.


您所期望的与实际发生的有什么不同?
Subtree generated commits are not signed, but signed commits is what I expected.


您想要补充的其它内容:
I think checking commit.gpgSign before generating each commit is a good start point for fix this.


I pushed to https://github.com/Akarinnnnn/SteamworksParser.
You can see from commit `a2883a6` on https://github.com/Akarinnnnn/SteamworksParser/commits/smart-anycpu-marshal are all not signed.
Which is the starting point I use git-subtree to manage internal module.




请检查下面错误报告中余下的内容。
您可以删除任何您不想共享的内容。
I think checking commit.gpgSign before generating each commit is a good start point for fix this.


By the way, I pushed subtree managed content to You can see from commit `a2883a6` on https://github.com/Akarinnnnn/SteamworksParser/commits/smart-anycpu-marshal are all not signed.
Which is the starting point I use git-subtree to manage internal module.


[系统信息]
git 版本:
git version 2.43.0.windows.1
cpu: x86_64
built from commit: 4b968f3ea3b32a7bc50846bab49f3f381841d297
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Windows 10.0 26200 
编译器信息:gnuc: 13.2
libc 信息:libc 信息不可用
$SHELL (typically, interactive shell): pwsh




[启用的钩子]
	
Best regards,
    Fa鸽

                 reply	other threads:[~2025-11-01 12:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tencent_D8444AABD439465DB4FA0D624A8E85A0220A@qq.com \
    --to=fa_ge-akarinnnnn@qq.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).