feat: Add root CONTRIBUTING.md to redirect users to official guide (Closes #11986) #12287
+27 −0
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.
Added guidelines for contributing to the project.
What does this PR do?
| Add info |
IMPORTANT
For resources
N/A. This PR adds a documentation file (CONTRIBUTING.md) to the root, not a resource (book/course) to a list.
Description
This PR is related to repository maintenance and contributor guidance. I'm adding a root-level CONTRIBUTING.md file to redirect contributors to the official, detailed guidelines hosted in the docs/ folder. This specifically resolves the contributor confusion mentioned in Issue #11986.
Why is this valuable (or not)?
Valuable: It improves the discoverability of the contribution guidelines. New contributors landing on the GitHub page will instantly see the link to CONTRIBUTING.md in the sidebar and the file content, addressing the current confusion about where the rules are located. This saves maintainers time answering basic contribution questions.
How do we know it's really free?
N/A. This PR adds a documentation file, not a programming resource.
For book lists, is it a book? For course lists, is it a course? etc.
N/A. This PR adds a repository maintenance guide.
Checklist:
Follow-up