Feature summary (what you would like to be able to do and where):
If enabled by the tool developer, push-to-deploy should log each deployment to the tool’s SAL. It should include the Git commit hash (abbreviated), and perhaps the subject line of the commit message too.

Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):
As a tool developer who currently logs deployments, I would like to still have a log of deployments once I start using push-to-deploy :)

Benefits (why should this be implemented?):

• feature parity with manual deployments in this particular respect
• more information about tool maintenance / current status / recent changes (e.g. if there are issues, tool users can check if they might be related to a recent deployment)

Note: if this isn’t built into push-to-deploy (initially?), it’s probably possible to emulate it via a separate script in the CI job (e.g. GitLab CI) that triggers the push-to-deploy.

(This task was created during Wikimedia-Hackathon-2025 out of a discussion between @aborrero and me.)