Skip to content

Add CI pipeline for format, clippy, and test#42

Merged
ScottMorris merged 3 commits intomainfrom
feat/ci-pipeline
Mar 18, 2026
Merged

Add CI pipeline for format, clippy, and test#42
ScottMorris merged 3 commits intomainfrom
feat/ci-pipeline

Conversation

@ScottMorris
Copy link
Copy Markdown
Contributor

Summary

  • Adds .github/workflows/ci.yml with four jobs: Format, Clippy, Test, and PR summary
  • Runs on every pull request to main, push to main, and manual dispatch
  • Uses bare ubuntu-24.04 runners with dtolnay/rust-toolchain@master pinned to workspace rust-version (1.94)
  • Tests run via cargo nextest with JUnit XML output, reported by EnricoMi/publish-unit-test-result-action and dorny/test-reporter
  • PR summary comment posted by a bot with per-job pass/fail status
  • Adds .config/nextest.toml (CI profile for JUnit output path)
  • Adds .node-version to control the GitHub Actions Node runtime without the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 env hack

Follows the org CI pattern established in emoji-nook and tauri-plugins-workspace.

Test plan

  • CI workflow runs on this PR and all three check jobs pass
  • JUnit test results appear as a check annotation on the PR
  • Bot comment with CI summary is posted
  • After merge, CI runs on the push to main

Related

🤖 Generated with Claude Code

Add format, clippy, and nextest jobs that run on every pull request
and push to main, matching the org CI pattern from emoji-nook and
tauri-plugins-workspace. Includes JUnit test reporting, per-job
summaries, and a bot comment on PRs with the outcome of each check.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@ScottMorris ScottMorris added ci CI/CD infrastructure Build systems, CI/CD, tooling, and shared infrastructure labels Mar 18, 2026
@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 18, 2026

Flow Tests

85 tests   85 ✅  0s ⏱️
 4 suites   0 💤
 1 files     0 ❌

Results for commit f2da239.

♻️ This comment has been updated with latest results.

dorny/test-reporter only matches files from git ls-files, so it
cannot see the JUnit XML in target/ (gitignored). The EnricoMi
publish-unit-test-result-action already covers test result reporting.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown

CI check summary

  • [PASS] Format: success
  • [PASS] Clippy: success
  • [PASS] Test: success

The junit.path in nextest config is relative to the profile output
directory (target/nextest/ci/), not the workspace root. Use just
"junit.xml" so the file lands at target/nextest/ci/junit.xml where
the workflow expects it.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@ScottMorris ScottMorris merged commit 9c6967b into main Mar 18, 2026
5 checks passed
@ScottMorris ScottMorris deleted the feat/ci-pipeline branch March 18, 2026 02:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci CI/CD infrastructure Build systems, CI/CD, tooling, and shared infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant