ci: rename CI/CD pipelines from moat to synapse#24
Merged
Conversation
Case-preserving moat -> synapse rename across the CI/CD workflows: - build.yaml workflow name: 'Moat Operator Build' -> 'Synapse Operator Build' - release.yaml env MOAT_OPERATOR_REGISTRY_IMAGE -> SYNAPSE_OPERATOR_REGISTRY_IMAGE - artifact moat-operator-bake-meta -> synapse-operator-bake-meta - temp file moat-bake-meta.json -> synapse-bake-meta.json - digests artifact moat-digests-* -> synapse-digests-* Upload/download artifact name pairs kept consistent. The published image ghcr.io/gen0sec/synapse-operator contains no 'moat' and is unchanged.
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.
Case-preserving
moat→synapserename across the GitHub Actions workflows.moatonly appeared insynapse-operator's two workflow files.build.yamlname:Moat Operator BuildSynapse Operator BuildMOAT_OPERATOR_REGISTRY_IMAGESYNAPSE_OPERATOR_REGISTRY_IMAGEmoat-operator-bake-metasynapse-operator-bake-metamoat-bake-meta.jsonsynapse-bake-meta.jsonmoat-digests-*synapse-digests-*docker-prepare → docker-build → docker-mergejob chain stays intact.ghcr.io/gen0sec/synapse-operatorcontains nomoat, so registry output is untouched.moatoccurrences remain (any case); both workflows still parse as valid YAML.