RFC 002: PR Contribution Guidelines#302
Open
chaodu-agent wants to merge 2 commits intoopenabdev:mainfrom
Open
Conversation
7d5a23e to
7ffcd81
Compare
951c3d3 to
e90afe2
Compare
Add RFC, PR template, and CONTRIBUTING.md requiring contributors to research OpenClaw and Hermes Agent before proposing solutions. - docs/rfcs/002-pr-guidelines.md — full RFC (follows RFC 001 format) - .github/pull_request_template.md — auto-populated PR form - CONTRIBUTING.md — contributor guide linking to RFC
e90afe2 to
d9cd2ac
Compare
|
All PRs must reference a prior Discord discussion to ensure community alignment before implementation. Please edit the PR description to include a link like: This PR will be automatically closed in 3 days if the link is not added. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What problem does this solve?
OpenAB is growing and accepting external contributions. Without a clear PR standard, we see PRs that jump straight to implementation without researching how existing projects solve the same problem, making reviews harder and risking reinventing the wheel.
What's in this PR
docs/steering/rfc-pr-guidelines.md.github/pull_request_template.mdCONTRIBUTING.mdKey decisions
Open questions (in the RFC)