ci: align workflow filenames on the estate standard - #52
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
1 participant
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.
Aligns this repo on the estate workflow naming standard - one reserved filename per role. See
playbooks/pipeline-naming.md.publish.ymlrelease.ymlrelease-train.ymltrain.ymlThe dispatch line is updated in the same commit. The train runs
gh workflow run publish.ymlby filename - renaming the file without that edit leaves the train departing every Friday while nothing publishes, and a dispatch to a missing workflow does not fail the train, so it would have been silent.Prerequisite already merged:
agentage/automation#397makes the Friday watchdog resolve the train workflow at runtime instead of hardcodingrelease-train.yml, so the guard keeps working across this rename.