-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
How to file a bug report
- Create a GitHub Account
- Access Oppia's GitHub Repository
- File a New Issue
- Engage in the Issue Discussion
- Conclusion
Welcome to Oppia's GitHub issue filing guide for non-developers! This step-by-step guide will help you navigate the process of creating a GitHub account and filing an issue on Oppia's GitHub repository. Let's get started!
-
Visit the GitHub website at https://github.com.
-
Click on the "Sign up" button to create a new GitHub account.
-
Follow the instructions provided by GitHub to complete the signup process.
-
Verify your account by clicking on the confirmation link sent to your email.
-
Open your web browser and go to Oppia's GitHub repository.
-
You will see the main page of the Oppia repository where the development and issue tracking take place.
-
On the Oppia repository page, locate the "Issues" tab near the top navigation bar and click on it.
-
In the "Issues" tab, you will find a green button labeled "New issue." Click on it to create a new issue.
-
Choose type of the issue which you want to file from the list of available types.
-
On the issue creation page, provide a concise and descriptive title for your issue in the "Title" field and follow the steps as mentioned along with each comment box.
Note: Red starred comment box means it must be filled.
-
If applicable, you can include screenshots or any other supporting files by dragging and dropping them into the comment box.
-
Once you are satisfied with your issue, click on the green "Submit new issue" button to file it.
-
After filing the issue, you will be redirected to the issue's page.
-
From this point, you can monitor updates and engage in discussions related to the issue.
-
To comment on the issue, scroll down to the comment section and enter your comment in the text box provided. You can share additional information, provide clarifications, or ask questions related to the issue.
-
If a developer requests additional information or clarification, you can respond by adding a comment.
-
Utilize the preview feature to review your comment before submitting it. Click on the "Preview" tab beside the comment box to see how your comment will appear. Make any necessary edits if required.
-
Once you are satisfied with your comment, click on the "Comment" button to post it.
-
Feel free to engage in the ongoing discussion by adding more comments as needed.
Congratulations! You have successfully filed an issue on Oppia's GitHub repository. Your contribution is valuable in improving Oppia for everyone. Remember to follow notifications and actively participate in the issue's discussion to help the developers fix it as soon as possible.
For further assistance or more information, you can refer to the GitHub Help Documentation.
Have an idea for how to improve the wiki? Please help make our documentation better by following our instructions for contributing to the wiki.
Core documentation
Developing Oppia
- FAQs
- Installing Oppia
- Getting started with the codebase
- Making your first PR
- Learning resources for developers
- Codebase Overview
- Coding Guidelines
- Coding style guide
- Guidelines for creating new files
- How to add a new page
- How to write frontend type definitions
- How to write design docs
- Revert and Regression Policy
- Server errors and solutions
-
Debugging
- If your presubmit checks fail
- If CI checks fail on your PR
- Finding the commit that introduced a bug
- Interpreting GitHub Actions Results
- Debugging Docs
- Debugging datastore locally
- Debugging end-to-end tests
- Debugging backend tests
- Debugging frontend tests
- Debug frontend code
- Debugging custom ESLint check tests
- Debugging custom Pylint check tests
- Debugging Stories
- Guidelines for launching new features
- Guidelines for making an urgent fix (hotfix)
- Lint Checks
- Oppia's code owners and checks to be carried out by developers
- Privacy aware programming
- Backend Type Annotations
- Bytes and string handling in Python 3
- Guidelines for Developers with Write Access to oppia/oppia
- Testing
- Release Process
Developer Reference
- Oppiabot
- Frontend
- Backend
- Translations
- Webpack
- Third-party libraries
- Extension frameworks
- Oppia-ml Extension
- Mobile development
- Mobile device testing
- Performance testing
- Build process
- Team structure
- Triaging Process
- Playbooks
- Wiki
- Past Events