Config as Code commits set two different identities: the author is the editing user (correct), while the committer is a shared Octopus identity (Octopus Deploy noreply@octopus.com) by default, or the signing key's identity if Git commit signing is configured.
This fails custom Git hooks that require the author and committer to match — a security control some organisations enforce on their Git hosting.
There is currently no setting to make the committer match the author. Configuring a commit signing key changes the committer, but to one fixed identity for the whole instance rather than to the editing user, so it does not satisfy such a hook unless every commit may share that identity.
Requested: an option to use the authoring user as the committer.
Config as Code commits set two different identities: the author is the editing user (correct), while the committer is a shared Octopus identity (Octopus Deploy noreply@octopus.com) by default, or the signing key's identity if Git commit signing is configured.
This fails custom Git hooks that require the author and committer to match — a security control some organisations enforce on their Git hosting.
There is currently no setting to make the committer match the author. Configuring a commit signing key changes the committer, but to one fixed identity for the whole instance rather than to the editing user, so it does not satisfy such a hook unless every commit may share that identity.
Requested: an option to use the authoring user as the committer.