Issues
There are some repos in the Answer project, you can raise your issue for different repos.
| Repo | Description | Issues |
|---|---|---|
| Answer | Answer core code | Issues |
| Answer Plugins | Answer plugins code | Issues |
| Answer Website | Answer website code | Issues |
When opening a new issue, always make sure to fill out the issue template. This step is very important! Not doing so may result in your issue not being managed in a timely fashion. Don't take this personally if this happens, and feel free to open a new issue once you've gathered all the information required by the template.
Please don't use the GitHub issue tracker for questions. Instead, you can ask your questions on Answer Meta, and we'll do our best to provide you with the answers you need.
Bugs
If you find a bug, the first thing to do is to search the issues to see if someone has already reported it. If so, please add any additional information as a comment on the existing issue.
If no existing issue exists, please open a new issue and fill out the issue template completely. The more information you provide, the more likely it is that your issue will be resolved quickly. Please include the following with each issue:
- A clear description of the problem
- A screenshot of the problem (if applicable)
- Steps to reproduce the problem
- The version of Answer you are using
- The deployment method you are using (e.g. Docker, binary, source)
- The version of your browser (if the issue is frontend-related)
- The operating system you are using (if the issue is backend-related)
- Any other details you think are relevant
Security bugs
If you find a security bug, with that in mind, please do not file public issues. You can follow the instructions in the security policy to report it privately.
Feature requests
We appreciate your feedback and ideas. If you have a feature request, please fill out the issue template completely and search the issues to see if someone has already requested the same feature.
If we think the feature request is a good idea, we'll add it to the roadmap and set the milestone. If you want to implement it, comment on the issue, and we'll assign it to you.
Issues labels
We use labels to categorize issues.
| Label | Description |
|---|---|
bug | Indicates an unexpected problem or unintended behavior |
documentation | Indicates a need for improvements or additions to documentation |
duplicate | Indicates similar issues, pull requests, or discussions |
feature | Indicates new feature requests |
enhancement | Indicates enhancement requests |
good first issue | Indicates a good issue for first-time contributors |
help wanted | Indicates that a maintainer wants help on an issue or pull request |
invalid | Indicates that an issue, pull request, or discussion is no longer relevant |
question | Indicates that an issue, pull request, or discussion needs more information |
wontfix | Indicates that work won't continue on an issue, pull request, or discussion |
security | Indicates a issue about security |