We are grateful for any contributions made by the community. Even seemingly small contributions such as fixing a typo in the documentation or reporting a bug are very appreciated!
Before reporting a bug, please try to first search existing GitHub issues to see whether your problem wasn't already discussed.
To report a bug, open a new GitHub issue. To report privately, e.g. to alert the maintainers about a security problem, please contact Apiary Support.
Before asking a question, please try to first search Dredd's documentation, Apiary Help.
You can always contact Apiary Support, but we prefer if you ask publicly, because it allows to spread the knowledge across the community of all Dredd users:
Also, we consider unclear or missing documentation to be a bug, so often your question can start a valuable improvement.
The documentation is written as code in the reStructuredText format and its source files are located in the docs directory. It is published automatically by the ReadTheDocs when the master branch is updated.
If you want to propose improvements to the documentation, you don't need to install the whole project. Usually it is just fine to use the GitHub's editing features.
When committing your changes, please use the prefix your commit message with docs:
docs: add more OpenAPI examples
You can learn more about Dredd's codebase in the Internals section of the documentation.
- Have Node.js installed
- Be familiar with Git, Pull Request flow and GitHub forks
- Read about Dredd's architecture
- Look at easy to fix issues
- Fork and clone Dredd
- Run
yarn install - Build Dredd with
npm run build - Write your code and tests
- Check your changes with
npm run lint && npm run test - Use the Conventional Changelog format for the commit message