This will be slightly annoying for everyone but I'm still considering this: Currently the tuf-on-ci workflows look like any other workflows and it would be nice if they were clearly separated by a name prefix
This is already the case in the actual name fields of the workflows so the Actions UI on Github looks fine (screenshot from root-signing-staging):
but the same is not true for the files -- it's impossible to tell which workflows are part of tuf-on-ci:
I would much rather that the tuf-on-ci workflows were named tuf-on-ci-create-signing-events.yml, tuf-on-ci-online-sign.yml, etc so it would be clear which workflows are projects own custom workflows and which ones are tuf-on-ci workflows.
I'm not 100% it's worth the annoying churn though: tuf-on-ci actions have to change and then all users need to do this rename that is probably easy to mess up.
This will be slightly annoying for everyone but I'm still considering this: Currently the tuf-on-ci workflows look like any other workflows and it would be nice if they were clearly separated by a name prefix
This is already the case in the actual name fields of the workflows so the Actions UI on Github looks fine (screenshot from root-signing-staging):
but the same is not true for the files -- it's impossible to tell which workflows are part of tuf-on-ci:
I would much rather that the tuf-on-ci workflows were named
tuf-on-ci-create-signing-events.yml
,tuf-on-ci-online-sign.yml
, etc so it would be clear which workflows are projects own custom workflows and which ones are tuf-on-ci workflows.I'm not 100% it's worth the annoying churn though: tuf-on-ci actions have to change and then all users need to do this rename that is probably easy to mess up.