Frequently Asked Questions

I’m new to GitHub and open source. Where should I start?

See our How to Contribute to Open Source Guide. It’s a beginner-friendly resource with tips for contributing to open-source projects.

What do I need to know to contribute to the codebase?

freeCodeCamp runs on a modern JavaScript stack. You should be familiar with JavaScript and the technologies we use: Node.js, MongoDB, OAuth 2.0, React, Gatsby, and Webpack.

Can I use AI tools to help with my contributions?

Yes, but use them productively.

We use tools like GitHub Copilot and Claude every day. Before you ask an AI assistant to modify code on your behalf, spend at least 10 minutes reading our contributing guidelines. Grounding the tool in our conventions—branch naming, commit style, pull request workflow, and testing expectations—saves you time on rework and makes your contribution easier to review.

Where AI is OK, and where it isn’t:

• OK in code: Use any tool to help you write, refactor, or debug.
• Not OK in comments and responses: We will not engage with contributors who reply through AI-generated content on issues, pull requests, or discussions.

How we handle low-effort contributions:

• We may apply a deprioritize label to pull requests that show low-quality or low-effort work. You are expected to address the gaps.
• We may close pull requests that don’t meet our standards without further discussion. This isn’t a punishment—it’s how we manage limited volunteer time.

TL;DR

Use any tool you want, but put in the effort. We value high-quality contributions and the time of every maintainer reviewing them.

How can I report a new bug?

If you think you’ve found a bug, read our How to Report a Bug article first and follow the instructions.

If you’re sure it’s a new bug, open a GitHub issue with as much detail as possible. Our issue template will guide you.

Note: GitHub issues are for code-related problems, not coding help. If unsure, ask in the forum before opening an issue.

How can I report a security issue?

Don’t open a GitHub issue for security concerns. Follow our security policy instead.

Where should I start if I want to work on an issue?

Browse the help wanted and first timers only labels for available issues.

Tip

• help wanted issues are open to anyone—no permission needed.
• first timers only issues are reserved for people who haven’t contributed to the freeCodeCamp codebase before.

I found a typo. Should I report an issue before making a pull request?

For minor typos or wording changes, open a pull request directly without creating an issue first. Include enough detail in the description to help us review.

For bigger changes, open an issue first to discuss.

How can I get an issue assigned to me?

We don’t assign issues unless you’re a long-time contributor. We follow this policy:

1. We merge the first pull request that fixes the issue.
2. If multiple pull requests arrive at the same time, we prioritize the one that best fixes the issue. We consider: Are tests included? Are all use cases covered? Does everything work and all tests pass?
3. We give priority to pull requests that follow our guidelines: Is the checklist followed? Is the title meaningful?

I’m a student. Can I work on a feature for academic credits?

Yes, but we cannot guarantee timelines or meet specific school requirements. We receive many contributions from volunteers and want to respect everyone’s time.

Plan ahead—we cannot prioritize school-related pull requests.

What do the different labels on issues mean?

Maintainers triage issues and pull requests by priority, severity, and other factors. See the full list of labels.

Can I translate freeCodeCamp’s resources?

Yes. You can help translate our resources into any of the 30+ languages we support.

We already have user-contributed translations in several languages and plan to add more. For background, see our announcement.

If you want to help, read this guide first.

Can I contribute articles to freeCodeCamp News or videos to freeCodeCamp’s YouTube channel?

Yes. Both are open to contributors.

For articles, see our publication guide and style guide.

For educational videos, follow the YouTube channel guide.

I’m interested in becoming a moderator at freeCodeCamp. Where should I start?

Community moderators keep freeCodeCamp welcoming. To become one, get involved in the community and follow our code of conduct.

Where to start:

• Discord/Chat moderators: Be active in chat, engage positively, and learn to manage conflicts.
• Forum moderators: Participate in the forum, help others, and give feedback.
• GitHub moderators: Review issues and propose solutions.

If you do this consistently over time, current moderators may recommend you and a staff member will reach out. Moderators and contributors are volunteers, so we value consistent engagement over 24/7 availability.

See our Moderator Handbook for detailed responsibilities and expectations.

Where can I get help if I’m stuck on something not covered here?

Ask for help in:

• The Contributors category of our community forum.
• The #Contributors channel on our chat server.

You can also ask questions on the relevant issue threads and we’ll clarify. Search for answers before posting new questions.

Thanks for being polite and patient—our community is run mostly by volunteers.