-
If the bug is a security vulnerability do not open up a GitHub issue but instead refer to our security policy.
-
Ensure the bug was not already reported by searching on GitHub under Issues.
-
If you're unable to find an open issue addressing the problem, open a new one. Please provide as much relevant information as possible including a precise title.
-
Open a new GitHub pull request with the patch.
-
Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
-
Before submitting, you can test locally whether the integration tests will (likely) pass. Simply enable the same Maven profiles as our CI pipelines.
-
Suggest your change in the discussions and start writing code.
-
Do not open an issue on GitHub until you have collected positive feedback about the change. GitHub issues are primarily intended for bug reports and confirmed feature requests.
- Ask any questions about how to use AutomataLib in the discussions.