.github — the Yellow Pine org profile

Organization-wide GitHub configuration for Yellow Pine. The company homepage is yellowpine.com. The org profile rendered from this repository is what every visitor to github.com/yellow-pine lands on, so it is held to the publish rule below and to the invariants in tests/ — but it is not the homepage itself.

Contents

• profile/README.md — the public org profile.
• brand/ — the canonical public brand library: hand-cleaned SVG masters (logo, dark variant, tile icon, bare mark), palette, and usage rules. The full Brandmark export archive and raster generators live in the private yellow-pine/brand-assets repo.
• tests/ — profile invariants, run by CI on every push and weekly: every referenced asset exists, brand SVGs are real vectors, every linked repo is publicly visible without auth (nothing private can leak onto the profile), and every product link is live.

The publish rule

A project is publishable — on the profile, on yellowpine.com, anywhere Yellow Pine speaks publicly — only if it is a public repo, or a private repo with a live public website. The rule is company-wide; what is scoped is the enforcement. The tests here cover the mechanical half for the profile: they fetch every github.com/yellow-pine/* link anonymously and fail on anything not public. The website repo inherits the rule and enforces it the same way against its own page.

npm test              # run the invariants locally
SKIP_NETWORK=1 npm test   # offline: skip the link-liveness checks