Describe the Feature
This is a cross project feature. I.e. it is not only for leverage.
I'm adding it here to keep track of this issue on planning meetings.
As per this thread, the automated actions on repositories, were assigned to specific users despite the fact they were done by 3rd party tools such as CircleCI or ArgoImageUpdater.
On Github machine users can be created to anonymize these actions.
Expected Behavior
Automated actions should not be pinned to a human user, instead a generic user (or one user per 3rd party tool) should be used.
Use Case
Argo Image Updater updates information on repositories. It is desirable to know the user who introduced the change is Argo and not a human one. (who is not aware of the change, maybe)
Describe the Feature
This is a cross project feature. I.e. it is not only for
leverage.I'm adding it here to keep track of this issue on planning meetings.
As per this thread, the automated actions on repositories, were assigned to specific users despite the fact they were done by 3rd party tools such as CircleCI or ArgoImageUpdater.
On Github machine users can be created to anonymize these actions.
Expected Behavior
Automated actions should not be pinned to a human user, instead a generic user (or one user per 3rd party tool) should be used.
Use Case
Argo Image Updater updates information on repositories. It is desirable to know the user who introduced the change is Argo and not a human one. (who is not aware of the change, maybe)