Skip to content

fix: derive home command count, check commands.json in CI - #6

Merged
ralyodio merged 1 commit into
mainfrom
fix/commands-json-generated
Oct 2, 2026
Merged

ralyodio merged 1 commit into
mainfrom
fix/commands-json-generated

Conversation

@ralyodio

@ralyodio ralyodio commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Home stats strip said 51 commands while /commands.json had 54 (the CLI's moshcode help --markdown table, byte-identical to its README block).

  • Stats count derived from data/commands.json (test added; failed before the fix).
  • CI runs bun run check on PR/push plus a daily cron, since the CLI repo changes its table without touching this one.
  • Sync source URL: master -> main (the CLI repo has no master branch; it only worked via redirect).

🤖 Generated with Claude Code

The home page stats strip still hardcoded 51 commands while
data/commands.json (and /commands.json) had 54. The count now comes from
the data. CI runs `bun run check` (sync-commands --check) on every PR,
push, and daily, so the JSON cannot silently fall behind the CLI's
generated README table. The sync source now points at the CLI's real
default branch (main) instead of relying on the master redirect.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ralyodio
ralyodio merged commit 3e0b89a into main Oct 2, 2026
3 checks passed
@ralyodio
ralyodio deleted the fix/commands-json-generated branch October 2, 2026 06:41
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.

1 participant