We appreciate your interest in contributing to Go Commandline Publisher! By contributing, you not only improve the project but also help the wider community.
If you encounter any bugs or have ideas for new features, please create an issue on our GitHub repository. When reporting a bug, please provide detailed information about the issue, including steps to reproduce it and the expected behavior.
We welcome pull requests from the community. If you want to contribute code to Go Commandline Publisher, follow these steps:
- Fork the repository on GitHub.
- Create a new branch from the
mainbranch for your changes. - Make your changes in the new branch.
- Ensure that your changes follow the project's coding guidelines and best practices.
- Write tests for your changes if applicable.
- Run the existing tests to ensure that they pass with your changes.
- Commit your changes with a descriptive commit message.
- Push your branch to your forked repository.
- Open a pull request on our repository and provide a clear description of your changes.
- Follow the existing code style and conventions used in the project.
- Write clear and concise code with meaningful variable and function names.
- Ensure that your code is well-documented with comments where necessary.
- Avoid introducing unnecessary dependencies.
- If you add new functionality, write tests to cover that functionality.
- Ensure that all tests pass before submitting a pull request.
After you submit a pull request, one or more project maintainers will review your changes. We appreciate your patience during this process, and we will do our best to provide timely feedback.
By contributing to Go Commandline Publisher, you agree that your contributions will be licensed under the project's BSD-style license.