-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
GitHub: Made CI/CD workflow run names more concise #16704
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
Conversation
Before: Files CD (Store Stable) / Deploy (Release, x64) After: Files CD / Deploy (Store Stable, Release, x64)
|
Looks like I broke the branch protection rule by renaming the CI 😄 |
|
I'm not in favor of this change at all. |
|
Why not? |
|
Because there are gonna be just 2 workflows, |
|
The capitalisation is inconsistent with the CodeQL workflows |
|
Doesn't matter, as far as it works, we should not change anything. |
|
This is how it's gonna be, I made a build script that covers all configurations. |
|
Changes to actions and similar tasks are currently on hold. Although it would be beneficial to improve these areas, our resources are limited, particularly with code review. Therefore, our focus is primarily on bug fixes and feature development. I don't have an exact timetable, but we should be able to put more time into these areas once the issue count is significantly lower. |
|
Yep that's why I even didn't open a PR (I made that branch a month ago). |
Resolved / Related Issues
Not worth opening another issue
Makes the CI/CD workflow names a bit more concise.
buildis nowBuildto be consistent