-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: Rename workflow names #27391
CI: Rename workflow names #27391
Conversation
d2df66a
to
f94d984
Compare
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I've added some comments below on general strategy, can do another pass later on specifics.
f94d984
to
5e69b54
Compare
This commit changes workflow's name fields to make them more human readable by adding spaces. Also some of the names was changed to be more consistent with each other Signed-off-by: Birol Bilgin <birol@cilium.io>
5e69b54
to
df0d946
Compare
/test |
Reviews in, failed tests are not related to the changes, setting as ready-to-merge |
@brlbil @nbusseneau how do we ensure consistency over time for these? I would like to avoid making rename changes like this as much as possible in future due to the disruption to PRs (renaming => have to rebase and rerun CI for every PR). Every time we create a new CI job there is a risk that we'll deviate again and then later on end up submitting a change again. We are still periodically adding more CI jobs. Is this something that @cilium/ci-structure will now enforce? |
I think yes, the right way forward would be to be stricter when doing reviews. |
This commit changes the workflow's name fields to make them more human-readable by adding spaces.
Also, some of the names were changed to be more consistent with each other.