This project relies solely on the community.
We'd love to have your contribution to deployd-cli. There are several ways to contribute:
- Help users on the chat
- Report bugs by creating an issue on github
- Write tests cases for open bugs and existing features
- Suggest and discuss new features
- Contribute to the documentation
This project and everyone participating in it is governed by the Deployd Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].
- chat on Gitter: Best chance to find someone to help you
- Q&A on stackoverflow
- Submit a bug on github
To help keep the issue count as low as it can be, it's important to first review closed issues to make sure the issue is unreported and valid.
When reporting a bug, fill out the form correctly using the template.
These are the guidelines for submitting pull requests for new features or bugs:
- Verify that the PR is not a duplicate to another PR
- Make all changes in a new git branch
- Follow the established Code Submission Standards
To ensure consistency in code style, keep these standards in mind as you work on code to submit to deployd:
- All features or bug fixes must be tested by one or more specs in the
test
directory - All public APIs must be documented in our docs
- ESlint should be run against all changes without warnings
Working on your first Pull Request? You can learn how from this free series How to Contribute to an Open Source Project on GitHub