Skip to content

Latest commit

 

History

History
38 lines (21 loc) · 1.55 KB

PR_workflow.md

File metadata and controls

38 lines (21 loc) · 1.55 KB

Workflow for Pull Requests

TL;DR: If your PR is ready to be pulled into the main branch, please click the “Ready for review” button.

We’re trying something new to keep great contributions from going stale.

🧭 The Problem

Many excellent PRs are submitted by contributors, but core maintainers have limited time for timely reviews. As a result, PRs often sit unmerged, contributors lose momentum, and valuable work risks being forgotten.

🛠️ The Solution: bleeding_edge Branch

We’ve created a bleeding_edge branch that automatically merges all PRs marked as ready.
“Ready” simply means the author has reviewed their own work and believes it’s fit for production.

  • All incoming PRs will initially be marked as Draft.
  • When your PR is ready, just click “Ready for review”.
    • If you're a returning contributor, and already know of this approach, you can also just say in your PR comments that your PR is ready to be pulled.
  • Your PR will then be automatically merged into the bleeding_edge branch.
  • Power users can install this weekly build to test multiple PRs together, helping catch issues earlier and reducing the load on core developers.

👉 Download bleeding edge builds

This approach allows us to:

  • Keep contributions fresh
  • Accelerate feedback loops
  • Empower the community to help stabilize new features

Thanks for helping make this project better.

Go here learn more about these bleeding_edge builds.