First off, thank you for considering contributing to the Regex Guide! 🤗🎉
Below, you’ll find guidelines. Following them helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests.
Note that the Regex Guide has adopted the Contributor Covenant as its Code of Conduct, and we expect you to adhere to it. Please read the full text so that you can understand what actions will and will not be tolerated.
All active development of the Regex Guide happens on GitHub. We actively welcome your pull requests.
If you think you’ve found a bug in the Regex Guide, please create a new issue. Please include as much detail as possible to help us properly address your issue. Help us be as efficient as possible by including a lot of detail in your issues.
Feature requests should be submitted in the issue tracker, with a description of the expected behavior & use case, where they’ll remain closed until sufficient interest, e.g. 👍 reactions, has been shown by the community. Before submitting a request, please search for similar ones in the closed issues.