Skip to content

Latest commit

 

History

History
35 lines (26 loc) · 2.08 KB

CONTRIBUTING.md

File metadata and controls

35 lines (26 loc) · 2.08 KB

Contributing Guidelines

Thank you for considering contributing to our project. To ensure that all contributors have a positive experience, we have established some guidelines that you should follow.

Before you begin contributing, make sure to read our Code of Conduct to understand how we expect community members to interact with each other.

How to Contribute.

  1. Fork the repository on GitHub.
  2. Create a branch in your fork with a descriptive name indicating the change you are making.
  3. Make the changes in your branch.
  4. Make sure your changes follow clean architecture patterns and coding best practices in Go.
  5. Run tests to ensure you haven't introduced any errors.
  6. Create a pull request from your branch to the main branch of the repository.
  7. Wait for the team to review your pull request. If changes are needed, make sure to make them before submitting a new review.
  8. Once your pull request is approved, the team will merge it into the main branch.

How to Report an Issue.

If you find a bug or issue in the project, please follow these steps to report it:

  1. Open an issue on the repository describing the problem as detailed as possible.
  2. Provide an example of the incorrect behavior and how it can be reproduced.
  3. Provide information about the environment in which you are running the code, including the version of Go you are using.
  4. If you have a solution for the problem, please submit a pull request following the guidelines established above.

Pull Request Guidelines

To ensure that pull requests integrate smoothly, please follow these guidelines:

  1. Follow the guidelines established in our Code of Conduct.
  2. Make sure your code follows Go's coding conventions, including formatting and style.
  3. Make sure your code follows clean architecture patterns and coding best practices in Go.
  4. Make sure your changes do not break any existing tests, and you have added tests for any new functionality.
  5. Create a detailed description of the changes you made and why you made them.

Thank you for contributing to our project. Your time and effort are greatly appreciated.