Skip to content

chore: sync develop → master (CI/DX hardening) - #53

Merged
aabrius merged 4 commits into
masterfrom
develop
May 28, 2026
Merged

aabrius merged 4 commits into
masterfrom
develop

Conversation

@aabrius

@aabrius aabrius commented May 28, 2026

Copy link
Copy Markdown
Contributor

Summary

Sync of 4 chore PRs already merged in develop. All are DX / CI infrastructure — none touch app or CLI source code. No version bump, no changesets, no publish triggered.

Commits being synced

# Title
#48 chore: ignore vitest browser snapshots, playwright artifacts and nyc output
#50 chore: add project .npmrc for @etus scope authentication
#51 chore: move CI checks to local pre-push to cut GitHub Actions usage
#52 chore: make coverage gate visible in pre-push hook

Impact on master

Area Before After
.gitignore Missing entries for vitest snapshots, Playwright artifacts, .nyc_output Now ignores them
.npmrc Missing — each clone depended on global ~/.npmrc Explicit @etus scope + token config in repo
.husky/pre-push 3 checks (typecheck + server tests + build) 8 checks (adds lint, client tests, template sync, CLI test/build) with visible coverage gate
.github/workflows/ 5 workflows 2 (release.yml, pr-target-check.yml) — others moved to local pre-push
Required check on master Code Quality (ghost, never reported) PR Target Check (real, ~5s)

Test plan

  • All 4 source PRs already passed local pre-push and merged into develop
  • No source code (src/, packages/*/src/) touched
  • No .changeset/*.md added — no publish will trigger
  • PR Target Check should pass automatically (develop is on the allowed-base list)

aabrius added 4 commits May 28, 2026 13:31
…output (#48)

* chore: ignore vitest browser snapshots, playwright artifacts and nyc output

Adds gitignore entries for test artifacts that are currently generated
locally but not tracked: vitest browser __screenshots__, playwright
blob results / video (.webm) / trace (.zip), and istanbul .nyc_output.

Salvaged from the closed PR #15, which had a valid .gitignore change
buried under an obsolete template sync.

* chore: sync template after gitignore update

- _gitignore: propagate the new test-artifact entries
- implement-issue.md: fix lingering reference to create-bhono-app
  (renamed to create-bhono in #45)

The "Verify Template is Synced" CI check fails on any diff under
packages/bhono-app/templates/, so the implement-issue.md drift had to
be included here.
Pins the @ETUS scope to the public npm registry and configures the auth
token explicitly, so install no longer depends on each developer's global
~/.npmrc or the CI runner's default registry.

@etus/* is published to registry.npmjs.org with restricted access — the
common 404 seen on fresh clones is missing org membership / token, not
a publish failure.

Also propagates the file into the bhono-app template so scaffolded
projects inherit the same explicit config.
#51)

Adds lint, client unit tests, template sync check, CLI tests and CLI
build to the local pre-push hook, and deletes the GitHub Actions
workflows that ran those same checks.

Local pre-push now covers everything the deleted workflows did:
- test.yml (Code Quality CLI) → CLI test + build steps
- template-sync-check.yml → sync:template:check step
- changeset-check.yml → covered by changesets release flow

Kept workflows: pr-target-check.yml (validates PR base, only knowable
server-side) and release.yml (needs NPM_TOKEN). Required status check
on master will be updated separately via gh api to point to "PR Target
Check".
Adds a header comment pointing to the vitest configs that own the
coverage thresholds, and renames the server/client test labels so it
is obvious those steps also enforce coverage — not just run tests.

No behavior change; gate was already enforced by vitest via the
--coverage flag in pnpm test:unit:server and test:unit:client.
@aabrius
aabrius merged commit 8e132d0 into master May 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants