Skip to content

docs: add CI status badge to README - #1

Closed
malekelkssas wants to merge 3 commits into
mainfrom
ci-verify/build-lint-test-check
Closed

malekelkssas wants to merge 3 commits into
mainfrom
ci-verify/build-lint-test-check

Conversation

@malekelkssas

Copy link
Copy Markdown
Contributor

Summary

  • Adds a CI status badge to the README, linked to the build-lint-test workflow.
  • Doubles as the phase 02 UAT trigger: opening this PR runs build-lint-test on GitHub's runners against the same commands verified locally in 02-VERIFICATION.md.

Test plan

  • build-lint-test job goes green on this PR (typecheck, lint, test, verify-lint-rules.mjs, verify-publish-shape.mjs, apps/example smoke test)

Also serves as the phase 02 UAT trigger for the build-lint-test
GitHub Actions job to run on a real PR.
Introduces a bare `effect` root-barrel import into a tracked
packages/**/src/**/*.ts file (not a fixture) to confirm the
build-lint-test Actions check fails red — ROADMAP Phase 2 success
criterion 5, verified as a GitHub-observed fact. Reverted in the
next commit.
@malekelkssas

Copy link
Copy Markdown
Contributor Author

Closing without merging: this PR's only real change (the CI badge) already landed on main via the full README rewrite in 48d251a, and main has since diverged enough (scope rename, publishConfig fix, README rewrite, ci.yml doc corrections) that GitHub now reports this branch as CONFLICTING against main. Nothing here is missing from main — it served its purpose triggering the three build-lint-test/release CI verifications for phase 02's UAT (see run history on this PR).

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