Description
GitHub automatically detects and surfaces certain community health files (CONTRIBUTING.md, CODE_OF_CONDUCT.md, LICENSE, etc.) as dedicated tabs/badges on the repository's main page only when they live at the repository root, in .github/, or in docs/ (per GitHub's documented community file locations). Checking this repository's rendered "Repository files navigation" and "Resources" sections confirms GitHub currently surfaces Readme, License, and Code of conduct as recognized community files — but not a "Contributing" tab, even though a real, apparently well-maintained contributing guide does exist at community/contributing-guidelines.md (a location GitHub's automated detection does not check).
This means every one of the standard GitHub UI affordances that funnel new contributors toward the contributing guide — the "Contribute" button dropdown, the community profile checklist, the new-issue template's automatic link — currently do not surface this project's actual contributing guide, even though it's referenced manually in the README three separate times.
Impact
New contributors arriving via GitHub's own UI prompts (not just the README) currently get no automatic pointer to the contributing guide, for a project explicitly trying to onboard as many GSSoC contributors as possible.
An easy, zero-content-change fix (just adding a file, or a redirect stub) with outsized discoverability impact given this repo's popularity (142 forks).
Proposed Solution
Add a CONTRIBUTING.md at the repository root that either contains the full guide directly, or is a short redirect stub pointing to community/contributing-guidelines.md (many large projects use this exact pattern to keep detailed content organized in a subfolder while still satisfying GitHub's auto-detection).
Verify, after merging, that GitHub's repository page now renders a "Contributing" entry in the Resources/Community Standards section (visible via the repo's Insights → Community Standards tab).
Acceptance Criteria
CONTRIBUTING.md exists at repo root (full content or redirect stub)
GitHub's Community Standards checklist (Insights tab) shows Contributing guidelines as ✅ present
No duplicate/conflicting content between the new root file and the existing community/contributing-guidelines.md
Description
GitHub automatically detects and surfaces certain community health files (CONTRIBUTING.md, CODE_OF_CONDUCT.md, LICENSE, etc.) as dedicated tabs/badges on the repository's main page only when they live at the repository root, in .github/, or in docs/ (per GitHub's documented community file locations). Checking this repository's rendered "Repository files navigation" and "Resources" sections confirms GitHub currently surfaces Readme, License, and Code of conduct as recognized community files — but not a "Contributing" tab, even though a real, apparently well-maintained contributing guide does exist at community/contributing-guidelines.md (a location GitHub's automated detection does not check).
This means every one of the standard GitHub UI affordances that funnel new contributors toward the contributing guide — the "Contribute" button dropdown, the community profile checklist, the new-issue template's automatic link — currently do not surface this project's actual contributing guide, even though it's referenced manually in the README three separate times.
Impact
New contributors arriving via GitHub's own UI prompts (not just the README) currently get no automatic pointer to the contributing guide, for a project explicitly trying to onboard as many GSSoC contributors as possible.
An easy, zero-content-change fix (just adding a file, or a redirect stub) with outsized discoverability impact given this repo's popularity (142 forks).
Proposed Solution
Add a CONTRIBUTING.md at the repository root that either contains the full guide directly, or is a short redirect stub pointing to community/contributing-guidelines.md (many large projects use this exact pattern to keep detailed content organized in a subfolder while still satisfying GitHub's auto-detection).
Verify, after merging, that GitHub's repository page now renders a "Contributing" entry in the Resources/Community Standards section (visible via the repo's Insights → Community Standards tab).
Acceptance Criteria
CONTRIBUTING.md exists at repo root (full content or redirect stub)
GitHub's Community Standards checklist (Insights tab) shows Contributing guidelines as ✅ present
No duplicate/conflicting content between the new root file and the existing community/contributing-guidelines.md