Skip to content

chore: slim public repo to distribution-only (smoke + notify CI, remove .internal)#19

Merged
FFawzy merged 2 commits into
mainfrom
claude/stupefied-wescoff-d3a12d
Jun 9, 2026
Merged

chore: slim public repo to distribution-only (smoke + notify CI, remove .internal)#19
FFawzy merged 2 commits into
mainfrom
claude/stupefied-wescoff-d3a12d

Conversation

@FFawzy

@FFawzy FFawzy commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator

What & why

Turns the public repo into a lean distribution mirror. Skills, commands, and vendor manifests are generated and synced in from a private repo via automated "chore(release): publish content" PRs, and the build/validate gate already runs upstream there before each release. So the public repo only needs the vendor dot-folders + their payload, minimal CI, and hand-owned README/LICENSE.

Changes

  • Delete .internal/ — the manifest generator, schemas, package.json, and build scripts. The dev→public release sync never touches .internal/ (not in the release allowlist), so removing it here is permanent and safe.
  • ci.yml → smoke tests only — dropped the validate job and all npm ci / npm run build steps (no generator to run; manifests are committed). Now just installs the Claude/Codex CLIs and validates the committed layout. Pinned Node 22; dropped the npm cache (no lockfile in this repo anymore).
  • notify-docs.yml — added a paths: filter so the docs repository_dispatch only fires on published content (skills, commands, vendor manifests, skills.sh.json). Editing README.md / LICENSE / .github/ no longer triggers a docs sync.
  • .github/workflows/README.md — updated to describe the distribution-mirror model.
  • .gitignore — reworded the comment that referenced .internal/ (rules unchanged).

Kept untouched: .claude-plugin/, .cursor-plugin/, .agents/, skills/, commands/, assets/, skills.sh.json, README.md, LICENSE, LICENSE-MIT.

Verification

Both vendor smoke tests pass locally against the committed layout (the same commands CI runs):

  • claude plugin validate ./ → ✔ Validation passed
  • codex plugin marketplace add ./ && codex plugin add commercetools@commercetools && codex plugin listcommercetools@commercetools installed, enabled

No .internal references remain; both workflow YAMLs parse cleanly.

Notes

  • .github/ is not in the dev release allowlist, so these workflow edits won't be overwritten by future release PRs.
  • Root assets/commercetools-symbol.svg is referenced by the Cursor manifest and is intentionally kept (hand-maintained — not part of the release sync).
  • Merging this PR will not fire notify-docs (changed paths don't match the new content filter).

🤖 Generated with Claude Code

Remove the .internal/ manifest generator and reduce CI to smoke tests plus
the docs notification. The build/validate gate already runs upstream in the
private dev repo before each release, and the release sync never touches
.internal/, .github/, README, or LICENSE — so the public repo only needs the
vendor dot-folders + their payload, minimal CI, and hand-owned README/LICENSE.

- Delete .internal/ (generator, schemas, package.json, build scripts)
- ci.yml: drop the validate job and npm build steps; smoke-test the committed
  layout only (claude plugin validate; codex install assertion); pin Node 22;
  drop the npm cache (no lockfile)
- notify-docs.yml: add a paths filter so README/LICENSE/.github edits don't
  trigger the docs sync
- update .github/workflows/README.md and tidy .gitignore

Both Claude and Codex smoke tests pass against the committed layout.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@FFawzy FFawzy self-assigned this Jun 9, 2026

@nkuehn nkuehn left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

trusting you :-)

@FFawzy FFawzy merged commit f65f7ba into main Jun 9, 2026
6 checks passed
@FFawzy FFawzy deleted the claude/stupefied-wescoff-d3a12d branch June 9, 2026 11:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants