Skip to content

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Remove bors #1131

wants to merge 1 commit into from

Conversation

curquiza
Copy link
Member

@curquiza curquiza commented Aug 5, 2025

Merge queue is already set up

Summary by CodeRabbit

  • Documentation

    • Removed references to Bors automation from contribution guidelines and the README badge section.
  • Chores

    • Deleted Bors configuration files and related patterns from workflow and release template settings.
    • Updated workflow triggers to only run tests on pushes to the main branch.

@curquiza curquiza requested a review from brunoocasali August 5, 2025 13:58
@curquiza curquiza added the maintenance Anything related to maintenance (CI, tests, refactoring...) label Aug 5, 2025
Copy link
Contributor

coderabbitai bot commented Aug 5, 2025

Walkthrough

This 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

Cohort / File(s) Change Summary
Bors Configuration Removal
bors.toml
Deleted the Bors configuration file, removing status checks and timeout settings for Bors merges.
Workflow Trigger Update
.github/workflows/tests.yml
Removed workflow triggers for Bors-related branches (trying, staging), restricting to main.
Release Draft Template Cleanup
.github/release-draft-template.yml
Removed replacer entries for Bors bot mentions from the release draft template configuration.
Documentation Update
CONTRIBUTING.md
Removed references and sections related to Bors automation for rebasing and merging PRs.
Badge Removal
README.md
Deleted the "Bors enabled" badge and its link from the README badges section.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A bunny hops—no Bors in sight,
The badges trimmed, the docs made light.
No bots to merge, no triggers set,
The garden’s calm, no workflow fret.
With carrots tall and code so clean,
The repo’s fresh, a tranquil scene!
🥕✨

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
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch remove-bors

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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 with main” requirement

With 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

📥 Commits

Reviewing files that changed from the base of the PR and between c5293d9 and 83a3988.

📒 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Anything related to maintenance (CI, tests, refactoring...)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant