Fix broken GitHub Actions after switch to MAINTAINER_LIST #23640
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Community Note
Relates #23636
Output from acceptance testing: n/a, relates to GitHub Actions
Information
The linked Pull Request updated several GitHub Actions to use the new
MAINTAINER_LIST
secret to pull a list of users for an exclusion list. Unfortunately, this broke many of the workflows, so this PR aims to fix it.There seems to be some inconsistencies, but the best I could tell, this is a result of using the
secrets
context injobs.<job-id>.if
definitions. Per the context availability docs this isn't supported (though it seemed to work on some Actions, so I'm still scratching my head a little).Because of that, this PR introduces a top level
env
definition that evaluates thecontains()
block (the same way we were doing it injobs.<job-id>.if
previously) and then moves the conditional tojobs.<job-id>.steps.if
, whereenv
is supported.