Repository navigation
Fix the .graphite.yml manifest for the registry sync - #1
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 platform's scheduled "Sync registry" workflow rejects this repository on every run with
Maat: .graphite.yml is not valid YAML: mapping values are not allowed here, so the registry entry is never created.What was invalid:
showcase.contributions,summary:was indented deeper thangithub:in the same list item, so YAML read it as a continuation of theOmar-Mohamed24scalar. This is the parse error.slug: ma'atfails the registry's slug pattern (^[a-z0-9](?:[a-z0-9-]{0,38}[a-z0-9])?$), and a top-level slug must equal the repository name in lowercase.What changed:
slugis nowmaat.namestaysMa'at.status: wip,listed: false, and the commented-out compose deploy block.[X]and[N]placeholders inshowcase.outcomeare left as they are for you to fill in.Validated by running the platform's
sync.applyagainst the current registry: 0 problems for this file, versus the parse error onmainand"ma'at" is not a valid slugwith the indentation fixed alone.