feat: opt into Blacksmith Linux runners#47
Conversation
Set use-blacksmith: true on the buildspace workflow call so release builds run on blacksmith-4vcpu-ubuntu-2404 instead of ubuntu-latest. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📜 Recent review details⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
🔇 Additional comments (1)
📝 WalkthroughWalkthroughThe release workflow now enables the Blacksmith tool by setting ChangesRelease Workflow Configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Review rate limit: 3/5 reviews remaining, refill in 20 minutes and 3 seconds. Comment |
There was a problem hiding this comment.
Pull request overview
This PR updates the release workflow’s reusable workflow call to opt into Blacksmith Linux runners for release builds, aligning the release build environment with the intended Blacksmith runner configuration.
Changes:
- Pass
use-blacksmith: trueto thephoton-hq/buildspacereusable release workflow to run release builds on Blacksmith Linux runners.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Set use-blacksmith: true on the buildspace workflow call so release
builds run on blacksmith-4vcpu-ubuntu-2404 instead of ubuntu-latest.
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com
Need help on this PR? Tag
@codesmithwith what you need.Summary by CodeRabbit