Contributing to SQL-Lifecycle-Management
SQL-Lifecycle-Management is open source software. We value feedback and 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
We use github to host code, to track issues and feature requests, as well as accept pull requests.
Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
- Fork the repo and create your branch from
main
. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite & linter checks pass.
- Issue that pull request and wait for it to be reviewed by a maintainer or contributor!
Report bugs using Github's issues
We use GitHub issues to track public bugs. Report a bug by opening a new issue.
Great Bug Reports tend to have:
- 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)
Start a discussion using Github's discussions
We use GitHub discussions to discuss about the current state of the code. If you want to propose a new feature, this is the right place to do it! Just start a discussion, and let us know why you think this feature would be a good addition to SQL-Lifecycle-Management (by possibly including some usage examples).
make test
Please ensure that all patches are accompanied by matching changes in the test suite. The project strictly maintains 100% test coverage.
By contributing, you agree that your contributions will be licensed under its Apache License.
This document was adapted from briandk's template.