-
Notifications
You must be signed in to change notification settings - Fork 418
feat(ci): add build workflow badge and improve workflow documentation #2063
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Co-authored-by: jcstein <[email protected]>
resolve conflicts @copilot |
resume pls @copilot |
I'll resolve the merge conflicts now and get this ready to merge. |
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Join our Discord community for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
Overview
This PR adds a build workflow status badge to the README and enhances the existing build workflow with better documentation, matching the implementation from rollkit/docs#469.
Problem
The repository already had a functional build workflow that catches build errors in CI, but it lacked visibility through a status badge. The existing workflow was working correctly but could benefit from clearer documentation about package manager alternatives.
Changes
.github/workflows/build.yml
with helpful comments showing package manager alternatives (yarn/pnpm/npm)How It Works
The build workflow runs on:
main
branchIt will fail with a non-zero exit code if:
yarn install
)yarn build
) due to syntax errors, missing files, configuration issues, etc.This provides reliable CI protection against build errors, ensuring that broken builds cannot be merged to main and that contributors get immediate feedback on build issues in their PRs.
Testing
yarn install
andyarn build
complete successfullyFixes #1739.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.