When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct, please follow it in all your interactions with the project.
Please review our code of conduct.
We use trunk based branching model that is aligned with todays DevSecOps practices.
All new features and/or fixes are merged into the main branch by creating a Pull Request.
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 (DO follow Microsoft Engineering Guidelines)
- Any changes or additions requires documentation in the form of documenting public members
- Ensure that all existing as well as new test passes
- Issue that pull request with a big and heartful thanks for contributing
We use GitHub issues to track public bugs. Please ensure your description is clear and has sufficient instructions to be able to reproduce the issue.
- Please follow Framework Design Guidelines
- Please follow SOLID principles
- Please follow Microsoft Engineering Guidelines
As aspiring Software Craftsmen we are raising the bar of professional software development by practicing it and helping others learn the craft.
Through this work we have come to value:
- Not only working software, but also well-crafted software
- Not only responding to change, but also steadily adding value
- Not only individuals and interactions, but also a community of professionals
- Not only customer collaboration, but also productive partnerships
That is, in pursuit of the items on the left we have found the items on the right to be indispensable.
Manifesto for Software Craftsmanship is the originator of this text.
By contributing to Extensions for Swashbuckle.AspNetCore API by Codebelt, you agree that your contributions will be licensed
under the MIT license.