Contributing to NebuCoders
Every project follows an open-source, issue-first workflow. This page covers what to expect before your first pull request. Want to propose something that doesn't exist yet instead? Pitch an idea →
From first message to maintainer
-
Join the community
Hop into Discord — that's the front door for everything.
-
Introduce yourself
Say what you want to build or learn. It's how people know where to point you.
-
Find your first issue
Check open issues across the org's repos, or ask — someone will have a beginner-friendly one.
-
Open a pull request
Link the issue it closes, keep it scoped to one change, and ask for a review.
-
Join a project
Consistent contributors get pulled into the core team working on that repo.
-
Maintain, mentor, lead
Leadership here is earned by sticking around and helping the next person — not appointed. We're building a rank system that links your GitHub to your Discord and tracks real PRs and commits toward this.
Planned, not live yet: linking your GitHub account to Discord so PRs and commits count toward a real rank — the path from contributor to maintainer, mentor, and project lead, based on what you've actually shipped.
Issue-first, always
Nothing gets built without an issue first. Before writing code, check the repo's issue tracker — pick up an existing issue or open a new one describing what you want to build.
If an issue doesn't exist yet, open one before starting work. It's how contributors avoid two people building the same thing.
What every repo expects
Branch naming
bugfix/fix-token-overflow
docs/update-contributing-guide
Pull requests
- Link the issue your PR closes
- Keep PRs scoped to one change
- At least one reviewer approval before merge
- CI checks must pass
Required files per repo
README.md— what the project does and how to run itCONTRIBUTING.md— how to contribute specifically to this repoLICENSE- Issue and pull request templates
Ready for your first issue?
Head to Discord and someone will point you to a good starting point.