Skip to content

Latest commit

 

History

History
34 lines (20 loc) · 1.72 KB

CONTRIBUTING.md

File metadata and controls

34 lines (20 loc) · 1.72 KB
Raw

How to contribute to TinyConfiguration

Did you find a bug?

  • Ensure the bug was not already reported by searching on GitHub under Issues.

  • If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.

Did you write a patch that fixes a bug?

  • Open a new GitHub pull request with the patch.

  • Ensure the pull request description clearly describes the problem and solution. Include the relevant issue number if applicable.

Did you fix whitespace, format code, or make a purely cosmetic patch?

Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of TinyConfiguration will generally not be accepted.

Do you intend to add a new feature or change an existing one?

  • Open a new Feature Request and tell us you are going to develop it
  • Wait for an approval, then go to the next step.
  • Start writing code, documentation and tests
  • Then make a pull request, it'll be approved or denied (mostly approved :D)

Do you have questions about the source code?

  • Ask any question about how to use TinyConfiguration at the following email.

TinyConfiguration is based upon one single developer.
I encourage you to take a step and start contributing to this library.
Thanks!

G. Baittiner