Skip to content

Latest commit

 

History

History
30 lines (21 loc) · 1.53 KB

File metadata and controls

30 lines (21 loc) · 1.53 KB

Contributing to Mints

Thanks for considering to contribute. We're open for any improvements.

Creating an issue

Use one of our issue templates to either submit a bug or request a feature.

Submitting a patch

To submit a minor change (bugfix), just create a pull request with a clear and concise description of what you're trying to address.

To submit a major change (feature, refactoring), link it with an open issue; consider creating one if needed.

Conventions

We appreciate clean and elegant code, and we love to follow some conventions in our journey.

Coding

  • Use docstrings for each new class or function.
  • Use Google Style docstrings.
  • Avoid creating utils or helper modules, classes or functions.
  • Avoid using get in method names. For example, get_item should be item.

Consider checking the source code for a more detailed picture.

Commits

  • Use clear and concise commit messages.
  • Start a commit message with a verb in the past tense, then describe the meaning of change, end with a period. For example, Added something., Cleaned up something., Removed something., Renamed `x` to `y`..

Note that we don't use the imperative style for messages.

Consider checking the commit history for a more detailed picture.