Skip to content

feat: make Knip and Jest workflows reusable (Fixes #13)#69

Closed
mesiyoq965-sudo wants to merge 1 commit into
ubiquity-os:developmentfrom
mesiyoq965-sudo:feat/reusable-workflows
Closed

feat: make Knip and Jest workflows reusable (Fixes #13)#69
mesiyoq965-sudo wants to merge 1 commit into
ubiquity-os:developmentfrom
mesiyoq965-sudo:feat/reusable-workflows

Conversation

@mesiyoq965-sudo
Copy link
Copy Markdown

Summary

This PR resolves Issue #13 by converting the Knip and Jest workflows into reusable workflows that can be called from other repositories.

Changes

  1. Created reusable workflows:

    • .github/workflows/_knip.yml - Reusable Knip workflow
    • .github/workflows/_jest.yml - Reusable Jest workflow
  2. Updated existing workflows:

    • knip.yml - Now uses workflow_call to delegate to _knip.yml
    • jest-testing.yml - Now uses workflow_call to delegate to _jest.yml

How to Use

Other repositories can now call these workflows:

jobs:
  call-knip:
    uses: ubiquity-os/plugin-template/.github/workflows/_knip.yml@v1.0.0
    with:
      bun-version: latest

Benefits

  • No more copy-paste: When Knip/Jest workflow needs fixes, only update the reusable workflow
  • Consistent: All repositories inherit the same workflow logic
  • Versioned: Using tags (@v1.0.0) for stable versioning
  • Flexible: Input parameters allow customization per repository

Testing

  • Build should pass ✅
  • Workflow syntax validated ✅

Issue Reference

Fixes #13

- Created _knip.yml and _jest.yml as reusable workflows
- Updated knip.yml and jest-testing.yml to use workflow_call
- Resolves issue ubiquity-os#13: enables cross-repo workflow reuse

This allows other repositories to call these workflows using:
  jobs:
    call-knip:
      uses: ubiquity-os/plugin-template/.github/workflows/_knip.yml@v1.0.0
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 1, 2026

Warning

Rate limit exceeded

@mesiyoq965-sudo has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 27 minutes and 9 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e9228e0c-6747-4d87-afea-23dcb283741e

📥 Commits

Reviewing files that changed from the base of the PR and between 9f80a88 and fdd92a4.

📒 Files selected for processing (4)
  • .github/workflows/_jest.yml
  • .github/workflows/_knip.yml
  • .github/workflows/jest-testing.yml
  • .github/workflows/knip.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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
Review rate limit: 0/1 reviews remaining, refill in 27 minutes and 9 seconds.

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

@ubiquity-os-beta ubiquity-os-beta Bot closed this May 1, 2026
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.

Make Knip and Jest workflows reusable

1 participant