Repository navigation
ci: add a ci-ok job for the ruleset to require - #4
Merged
Merged
Conversation
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
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.
What and why
Adds a
ci-okjob toci.yml: the single check theprotect-mainruleset can require (same name as in limen-dev/limen#326 and limen-dev/terraform-provider-limen#13). Itneedsevery other job, runs withalways(), and fails if any of them failed or was cancelled. Nothing in this workflow is path-filtered, so no orchestrator is needed here.A draft PR runs nothing, so
ci-okis skipped there, as the other jobs are.How it was verified
actionlintclean.Not verified
ci-okinprotect-mainonce it is green on a PR.Rollback
Revert this commit. Nothing is required yet.