Skip to content

Latest commit

Β 

History

History
87 lines (60 loc) Β· 2.5 KB

File metadata and controls

87 lines (60 loc) Β· 2.5 KB

Contributing guide

πŸ§‘β€πŸ¦± Contributions are welcome!

πŸ—’οΈ Table of content


πŸ‘¨β€πŸ’» Code contribution

To contribute code to the project, follow these steps:

  1. Open issues section and choose an issue to work on.
  2. Fork the repository on GitHub.
  3. Clone your forked repository to your local machine.
  4. Create a new branch for your changes.
  5. Install dependencies with make build (required to have make and go (version from go.mod) installed)
  6. Complete an issue and commit it.
  • Follow the style guide.
  • Test your code thoroughly.
  • Write clear and concise commit messages.
  1. Push your changes to your forked repository.
  2. Create a pull request to the main repository.
  • Pull request will not be merged until it is approved by a maintainer and passes all checks.

[List of code contributors] is updated weekly.

To make a code contribution, build the project:

Clone from GitHub

git clone git@github.com:statloc/cli.git

Install dependencies (requires make to be installed, go version is 1.25.1)

make build

Run linter and tests

make

To become a maintainer:

  1. Open an issue from a template.
  2. Provide a brief description of your contributions and experience.
  3. Wait for a response from the maintainers.

Alternatively, contact one of the maintainers from the maintainers list and request a maintainer role.


πŸͺ² Reporting a bug

To report an unexpected behavior, follow these steps:

  1. Open an issue from a template.
  2. Provide a description of the unexpected behavior following the template.
  • Fill as many fields as possible.

To report a security issue, follow these steps:

⚠️ DO NOT REPORT SECURITY ISSUES VIA GITHUB ISSUES!!!⚠️

To report a vulnerability or any other security issue, please contact any code owner from this list.


🀝 Feature suggestion

To suggest a feature, follow this steps:

  1. Open an issue from a template.
  2. Provide a description of the feature following the template.
  • Fill as many fields as possible.