Skip to content

chore: align CI with wolfstar.rocks conventions and add knip#63

Open
RedStar071 wants to merge 1 commit into
mainfrom
chore/improve-workflows
Open

chore: align CI with wolfstar.rocks conventions and add knip#63
RedStar071 wants to merge 1 commit into
mainfrom
chore/improve-workflows

Conversation

@RedStar071

Copy link
Copy Markdown
Member

🔗 Linked issue

N/A

🧭 Context

The CI workflow should follow the same conventions used across other Wolfstar projects (notably wolfstar.rocks), while keeping the library monorepo stack (pnpm, turbo, vitest, oxlint, changesets).

📚 Description

This PR realigns .github/workflows/ci.yml with wolfstar.rocks CI conventions and adds unused-code detection via Knip.

Key changes

Area Before After
Triggers push to main, all PRs PRs to main/release, push to main, merge_group on main
Concurrency Cancel only on PRs Always cancel in-progress runs
Runners ubuntu-latest ubuntu-24.04-arm
Job naming Plain names Emoji-prefixed names (lint, build, unit, knip, changesets)
Codecov Separate upload job + artifact Inline upload of JUnit results and Clover coverage in the unit test job
Unused code Not checked New knip job with root knip.json configuration
Problem matchers oxlint/oxfmt matchers in lint job Removed (tsc matcher kept for typecheck)
.gitignore Ignore test artifacts (*.junit.xml, grouped coverage/)

Type of Change

  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation change
  • Workflow / CI change

Pre-flight Checklist

  • I have read the Contributing Guidelines (if applicable)
  • My code follows the code style of this project
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have updated the documentation accordingly
  • I added a changeset with pnpm changeset (or pnpm changeset add --empty if no release is needed). See .changeset/README.md.

@changeset-bot

changeset-bot Bot commented Jun 26, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: b376e10

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai

coderabbitai Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@RedStar071, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 34 minutes and 41 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 8ee72ae9-16cb-44bd-af75-cc8eb8385144

📥 Commits

Reviewing files that changed from the base of the PR and between da0a1aa and b376e10.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (6)
  • .github/problemMatchers/oxfmt.json
  • .github/problemMatchers/oxlint.json
  • .github/workflows/ci.yml
  • .gitignore
  • knip.json
  • package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/improve-workflows

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@codecov

codecov Bot commented Jun 26, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 41.00%. Comparing base (da0a1aa) to head (b376e10).
✅ All tests successful. No failed tests found.

❗ There is a different number of reports uploaded between BASE (da0a1aa) and HEAD (b376e10). Click for more details.

HEAD has 1 upload less than BASE
Flag BASE (da0a1aa) HEAD (b376e10)
1 0
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #63      +/-   ##
==========================================
- Coverage   49.54%   41.00%   -8.54%     
==========================================
  Files          49       49              
  Lines         870      856      -14     
  Branches      200      193       -7     
==========================================
- Hits          431      351      -80     
+ Misses        435      338      -97     
- Partials        4      167     +163     
Flag Coverage Δ
unit 41.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

1 participant