An operator sets, per forge connection, the commit author name and email and an SSH signing key (secret reference) in the dashboard. Commits the daemon makes through that connection carry that identity and an SSH signature that git verify-commit and the forge accept. The key never enters a task container.
Done when a configured connection produces signed, attributed commits.
An operator sets, per forge connection, the commit author name and email and an SSH signing key (secret reference) in the dashboard. Commits the daemon makes through that connection carry that identity and an SSH signature that git verify-commit and the forge accept. The key never enters a task container.
Done when a configured connection produces signed, attributed commits.
Follow-up fa76f4c99: agent commits are made inside the container, so the identity and signature never applied. The daemon now re-authors and SSH-signs the unpublished commits at push time.
Follow-up fa76f4c99: agent commits are made inside the container, so the identity and signature never applied. The daemon now re-authors and SSH-signs the unpublished commits at push time.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
An operator sets, per forge connection, the commit author name and email and an SSH signing key (secret reference) in the dashboard. Commits the daemon makes through that connection carry that identity and an SSH signature that git verify-commit and the forge accept. The key never enters a task container.
Done when a configured connection produces signed, attributed commits.
Done in
ac98b68bd. Verified a signed commit with git verify-commit against an allowed-signers file.Follow-up
fa76f4c99: agent commits are made inside the container, so the identity and signature never applied. The daemon now re-authors and SSH-signs the unpublished commits at push time.