.github/workflows: add Blacksmith testbox configuration#4070
Conversation
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughA new Markdown skill document is added at ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
Thanks for your contribution! We require all external PRs to be opened in draft status first so you can address CodeRabbit review comments and ensure CI passes before requesting a review. Please re-open this PR as a draft. See CONTRIBUTING.md for details. |
|
|
||
| steps: | ||
| - name: Begin Testbox | ||
| uses: useblacksmith/begin-testbox@v2 |
| run: pnpm exec oxlint . | ||
|
|
||
| - name: Run Testbox | ||
| uses: useblacksmith/run-testbox@v2 |
| pull_request: | ||
| paths: | ||
| - '.github/workflows/**' |
There was a problem hiding this comment.
🚩 Workflow triggers on all workflow file changes, not just its own
The pull_request trigger at .github/workflows/code-quality-testbox.yml:10-11 uses paths: '.github/workflows/**', meaning any PR that modifies any workflow file (not just this one) will trigger this testbox workflow. This is likely intentional to validate the testbox workflow itself stays functional, but it does add an extra CI job to every workflow-touching PR. The existing code-quality.yml is a workflow_call (reusable workflow) so it doesn't have this path-trigger pattern to compare against.
Was this helpful? React with 👍 or 👎 to provide feedback.
Blacksmith Testboxes let your agents run CI against local changes, instantly.
This PR adds
.github/workflows/code-quality-testbox.ymland theblacksmith-testboxagent skill (.claude/skills/blacksmith-testbox/SKILL.md).