-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
GitHub Actions: Tidy workflow files #23955
Conversation
@@ -1,4 +1,4 @@ | |||
name: "Issue triage" | |||
name: 'Triage: Issues' |
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.
Perhaps
name: 'Triage: Issues' | |
name: 'Issues: Auto-triage' |
Because it is more likely that we'll add more workflows about issues than about triaging things
(Oops, just too late... maybe for next PR)
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.
I went with the "Triage" prefix because I figured we might triage PRs at some point, but we can always change to the "Issue" prefix if we end up with lots of issue-based workflows.
Backport of musescore#23955 Disable translate_tx_pull_to_s3.yml
Tidy the workflow files in preparation for #23067 (I'll introduce more workflows for that, but the current ones are a bit messy).
BUILD_MODES
variable.The new workflow names are sorted alphabetically to make them easier to find in the GitHub Actions list.