Skip to content

Fix the .graphite.yml manifest for the registry sync - #1

Merged
AmrMsCLL merged 1 commit into
mainfrom
fix/graphite-manifest
Nov 6, 2026
Merged

AmrMsCLL merged 1 commit into
mainfrom
fix/graphite-manifest

Conversation

@AmrMsCLL

@AmrMsCLL AmrMsCLL commented Nov 6, 2026

Copy link
Copy Markdown
Member

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:

  • Under showcase.contributions, summary: was indented deeper than github: in the same list item, so YAML read it as a continuation of the Omar-Mohamed24 scalar. This is the parse error.
  • slug: ma'at fails 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.
  • Indentation was inconsistent across the file (4, 6, 10 and 14 spaces at the same levels).

What changed:

  • slug is now maat. name stays Ma'at.
  • The whole file uses 2-space indentation like the other Project Graphite manifests; every value is otherwise unchanged, including status: wip, listed: false, and the commented-out compose deploy block.
  • The [X] and [N] placeholders in showcase.outcome are left as they are for you to fill in.

Validated by running the platform's sync.apply against the current registry: 0 problems for this file, versus the parse error on main and "ma'at" is not a valid slug with the indentation fixed alone.

@github-actions github-actions Bot added the size/m 51-200 changed lines, excluding lockfiles label Nov 6, 2026
@AmrMsCLL
AmrMsCLL merged commit 56bd926 into main Nov 6, 2026
8 of 9 checks passed
@AmrMsCLL
AmrMsCLL deleted the fix/graphite-manifest branch November 6, 2026 23:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/m 51-200 changed lines, excluding lockfiles

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant