How to Report a Bug to the freeCodeCamp open source community

Thank you for taking the effort to report an issue with freeCodeCamp.

If you think you’ve found a bug on freeCodeCamp, please follow these steps to resolve your problem:

  1. Try resetting the code in the editor using the reset button on the page. This will solve most of the issues if somehow you changed some code, that is affecting the challenge in some way. Resetting clears the code to its original state as if the challenge was first presented to you.

  2. If the page seems broken in any way, try to do a Hard Refresh of the page. This will update any old code that may have been cached in your browser.

  1. Ask for Help the Chat Rooms. You can usually get a quick response from a helpful community member there.

  2. Ask for Help on Forum. Occasionally you may see that your queries are not addressed on the chat right away, or it may be something that needs a discussion. In that case, make sure you search this forum for your issue and if you fail to find and satisfactory answer, then ask it here.

  3. If your problem has baffled everyone in chat rooms and the forum, try Searching for Your Issue on GitHub for anyone who has posted about a similar issue. If someone has, you can upvote the issue by clicking the (:thumbsup:) icon on the opening post (first post) in the issue thread.

  4. If you can’t find any relevant issues on GitHub, then Create a New Issue and our development team will take a look at your problem.

Some challenges may not work on mobile devices (mobile browsers), we try our best to support them, but we recommend that you try and check the challenge on a desktop browser before confirming as a bug.

Before you report a new issue always get a third party confirmation from someone in the chat rooms or the forum. Remember that the issue tracker is strictly for reporting bugs or enhancements, it’s not a place to seek any help with solving the challenges.