👍🎉 First off, thanks for taking the time to contribute! 🎉👍
We want to make contributing to this project as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Becoming a maintainer
The following is a set of guidelines for contributing to Whispir and its projects, which are hosted in the Whispir Organization on GitHub. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
I don't want to read this whole thing, I just have a question!!!
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
Note: Please don't file an issue to ask a question. You'll get faster results by using the resources below.
We have an official Github Discussions where Whispir Node API support and the community chimes in with helpful advice if you have questions.
- API Documentation
- Github Discussions
- Stackoverflow - Whispir related
- Submit requests for support to our API Support team.
You can contribute by reporting bugs, suggesting enhancements, improving documentation i.e. README or submitting a pull request.
Bugs are tracked as issues in this repository.
Before opening a new issue:
-
check the README to see if the behavior you observed might be expected and if configuration options are available to provide you with the desired behavior.
-
perform a cursory search to see if there's an existing issue covering your feedback. If there is one and the issue is still open, add a 👍 reaction on the issue to express interest in the issue being resolved. That will help the team gauge interest without the noise of comments which trigger notifications to all watchers. Comments should be used only if you have new and useful information to share.
- Which version of the SDK are you using?
- A quick summary and/or background
- Steps to reproduce
- Be specific!
- Give sample code if you can.
- What you expected would happen
- What actually happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
When opening an issue for a feature request:
- use a clear and descriptive title for the issue to identify the problem.
- include as many details as possible in the body. Explain your use-case, the problems you're hitting and the solutions you'd like to see to address those problems.
We welcome your feedback and pull requests. Be aware some code is generated and pull requests may not be the best solution - see below.
The best way to propose changes to the codebase is to open an issue and discuss with our team.
We are using OpenAPI Generator and our OpenAPI specs, to create and update our models and client classes. Improvements may require updates to our OAS or our customized mustache templates instead of modifying via pull request.
- Fork and clone the repository
- Create a new branch:
git checkout -b my-branch-name - Make your change, add tests if needed
- Push to your fork and submit a pull request
- Pat your self on the back and wait for your pull request to be reviewed and merged.
Here are a few things you can do that will increase the likelihood of your pull request being accepted:
- Follow the style guide.
- Write tests.
- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
- Write a good commit message.
- 4 spaces for indentation rather than tabs
By contributing, you agree that your contributions will be licensed under its MIT License.