Any contribution to improve Replay Reader is highly appreciated.
If you want to ask a question, we assume you have read the README.
Before you ask a question, it is best to search for existing Issues that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
If you then still feel the need to ask a question and need clarification, we recommend the following:
- Open an Issue.
- Provide as much context as you can about what you're running into.
- Provide project and platforms (Windows, Linux, MacOS), depending on what seems relevant.
We will then take care of the issue as soon as possible.
When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
If you find a bug in the source code, you can help by submitting an issue. You can also submit a pull request with a fix.
Before you submit an issue, please search the issue tracker. An issue for your problem may already exist and has been resolved.
Fixing all the issues as soon as possible is a goal, but before fixing a bug context needs to be shared to help to reproduce the issue. It saves a lot of time.
A minimal reproduction allows to quickly confirm a bug as well as confirm that we are fixing the right problem.
- Make sure the bugfix / feature you are trying to push is not already in the list, to avoid duplicates (a simple searsh should do).
- Make sure that the project build and test passes.
You can start contributing on an opened issue. For that, fork the project and create a pull request linked to that issue.
If you don't find an Issue for your idea of Feature, before even starting to work on it, open an Issue. We'll take a look and decide if the feature is needed or not to avoid you to lose time if we don't want to add that kind of feature.