We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
- Proposing new resources
- Reporting a bug
- Submitting a fix
We use github to create a bot, to track issues as well as accept pull requests.
Pull requests are the best way to propose new features and propose new hashtags to the codebase. We actively welcome your pull requests:
- Fork the repo and create your branch from
main. - Add One Feature per pull request.
- Pull request should include a short description.
- Issue that pull request!
In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.
Report bugs using Github's issues
We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!
Great Bug Reports tend to have:
- A quick summary and/or background
- Be specific!
- 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)
People love thorough bug reports. I'm not even kidding.
Kindly follow a conventional commit style for all commit messages and descriptions for this repository. Conventional commits play a huge role in understanding important changes to the source code. The more informative a commit, the better.
Examples of good commit messages are:
chore(repo): nest new devops-twitter-botfeat(hashtag): add hashtag #devops to one of the target hashtags- ...
Kindly go through the following resources to gain more information on the same:
By contributing, you agree that your contributions will be licensed under its MIT License.