Same, surprised it isn’t higher prio given signed commits are a given in any remotely security-conscious company.
It seems setting a special variable containing the signing secret should be sufficient to then have git sign with that via the agent.
Same, surprised it isn’t higher prio given signed commits are a given in any remotely security-conscious company.
It seems setting a special variable containing the signing secret should be sufficient to then have git sign with that via the agent.
Good news, Cursor cloud agents will now make signed commits! This applies to all new cloud agent runs going forward, you do not need to enable anything.
Just double-checked here, seems to be working! ![]()