-
Notifications
You must be signed in to change notification settings - Fork 94
Remove bors #1131
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
base: main
Are you sure you want to change the base?
Remove bors #1131
Conversation
WalkthroughThis set of changes removes all Bors-related configuration, documentation, and references from the repository. The Bors badge is deleted from the README, the bors.toml configuration file is removed, and workflow triggers for Bors branches are eliminated. Documentation is updated to reflect the absence of Bors automation. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
CONTRIBUTING.md (1)
109-112
: Clarify the “up-to-date withmain
” requirementWith Bors gone, contributors may be unsure how to keep their branch aligned. Consider appending a short note (or link) that explains acceptable ways to re-sync—e.g.
git rebase main
locally or the “Update branch” button in the GitHub UI. This avoids confusion and ensures the policy is actionable.- The branch related to the PR must be **up-to-date with `main`** before merging. + The branch related to the PR must be **up-to-date with `main`** before merging (e.g. rebase your branch on `main` locally or use GitHub’s “Update branch” button).
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (5)
.github/release-draft-template.yml
(0 hunks).github/workflows/tests.yml
(0 hunks)CONTRIBUTING.md
(1 hunks)README.md
(0 hunks)bors.toml
(0 hunks)
💤 Files with no reviewable changes (4)
- bors.toml
- .github/release-draft-template.yml
- .github/workflows/tests.yml
- README.md
Merge queue is already set up
Summary by CodeRabbit
Documentation
Chores