Repository navigation
docs: register through the hourly sync and write compose.yaml and values in platform - #7
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.
The README's setup checklist still told a new project to push
.graphite.yml"through the Registry workflow", which no longer exists inactions, and to adddeploy/<slug>/core.yamlandvalues.yaml, which the platform's plain compose path replaced.Changes
platform's hourly Sync registry, sooner when the Hub's webhook dispatches it.deploy/<slug>/compose.yamlovershared/andvalues; secrets entered in the console; apagessite's values hold onlyIMAGE_TAG.compose.yamlandIMAGE_TAGinvalues.Only the README changes;
pipeline.ymlalready calls the currentreusable-pipeline.yml.