Detach global deploy keys from admin user who created them
Problem to solve
An admin user account created global deploy keys with read-write privileges for use in automated scripts. Some scripts push to repositories every 15 minutes. Every time the script executes a push, it shows as activity by the admin user and notifies that user.
This activity drowns out the actual activity of the admin user, and doesn't depict the actual activity - of the automated script. It would be preferable not to attach the global deploy keys to the admin who created them.
Proposed in this ticket: https://gitlab.zendesk.com/agent/tickets/120055 (internal use only)
Intended users
Admin users of GitLab creating global deploy keys
Further details
From the user:
I always get notifications like "You pushed to yesss-deva1-search01 at Operations / etckeeper just now" in my gitlab web interface. This is annoying, because I don't see my own changes anymore.
Also, all those pushes are recorded as activity of my user account, but clearly these are not mine.
Proposal
The deploy keys should be associated with either a robot "user" or a group.
What does success look like, and how can we measure that?
The deploy keys are not associated with my user account and I do not get notifications or activity recorded for pushes done with the deploy key.