Hi stranger, thanks for your love.
If you're looking to improve g
, be sure to first:
- Search through Pull-Requests and Issues; someone might have had the same problem already.
- Read the LICENSE.
- Read the Code of Conduct.
- Check the
next
branch and what changes are pending for release, if any.
IMPORTANT: If you want to add a feature, please open an issue to discuss it first; g
aims to be simple.
Once you're ready to start coding:
- Fork the repo.
- Clone your fork.
- Checkout the
next
branch. - Apply your changes.
- Document your changes (README, CHANGELOG, --help, etc) where necessary.
- Run
make lint
to check the code withshellcheck
and runmake format
afterwards to style it withshfmt
.
Once you are done with your changes and cleared by make lint
and make format
:
- Commit with a meaningful message. See: How to Write a Git Commit Message.
- If your contribution is related to an existing issue, remember to reference the issue number.
- Push.
- Open a pull request against the
next
branch. - Ask for review.
- Be patient.
Love. ♥