Separate into reusable workflows so we can schedule CI for release branches#3570
Merged
Separate into reusable workflows so we can schedule CI for release branches#3570
Conversation
maxkadel
changed the title
In order to re-use workflows, separated existing configuration into reusable workflows. TODO: Allow more of the matrix to be configurable, especially the "include" stanza.
jcoyne
approved these changes
Apr 18, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
See this workflow run for an example of what will happen if one of the release-8.x CI runs fails.
In order to re-use workflows, separated existing configuration into reusable workflows.
TODO: Allow more of the matrix to be configurable, especially the "include" stanza. Once the release-7.x branch is green, this will be needed to add that branch to this configuration.
It could also be worth it to put these actions into their own repo in the projectblacklight namespace, and try to configure some of the plugins to use them as well, which could help with compatibility snarls, but that's a bigger project.