Thank you for considering contributing to Golden! We appreciate your time and effort in making this project better.
- Code of Conduct
- How Can I Contribute?
- Development Setup
- Pull Request Process
- Code Style
- Testing
- Documentation
- Community
- License
Please note that this project adheres to the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].
If you encounter a bug, please open an issue on the GitHub issue tracker with a detailed description of the problem, steps to reproduce, and any relevant information.
If you have ideas for enhancements, new features, or improvements, we welcome your suggestions. Please open an issue to discuss your ideas and gather feedback from the community.
Feel free to improve documentation, add how-tos or recipes. Also, feel free to write blog entries describing Golden, record screencasts or whatever contribution that can help others to use Golden in their own projects.
If you want to contribute code to Golden, follow these steps:
- Fork the repository on GitHub.
- Clone your forked repository to your local machine.
- Create a new branch for your changes:
git checkout -b feature/your-feature
. - Make your changes and ensure that the code follows the code style.
- Write tests to cover your changes.
- Ensure all tests pass:
go test ./...
. - Update the documentation if necessary.
- Push your changes to your forked repository.
- Create a pull request against the
main
branch of the main repository.
- Normalizers: that convert posible outputs to be persisted as snapshots.
- Scrubbers: to manage non-deterministic outputs.
- Reporters: to show the differences between the snapshot and the current output.
To set up your development environment, follow these steps:
- Clone the repository:
git clone https://github.com/franiglesias/golden.git
. - Change to the project directory:
cd golden
. - Install dependencies:
go get -u ./...
.
- Ensure your pull request addresses a specific issue or is well-described.
- Follow the code style guidelines.
- Include relevant tests for your changes.
- Ensure all tests pass before submitting the pull request.
- Update the documentation if needed.
- Squash your commits into a single commit.
As a general rule, follow the recommendations of Effective Go
Make sure to run tests before submitting a pull request:
go test ./...
Also, make sure that all new code is covered with tests.
Keep the project documentation up-to-date. If you make changes that require documentation updates, please include those changes in your pull request.
Join Project Discussions to discuss development, ask questions, or share your experiences.
By contributing to Golden, you agree that your contributions will be licensed under the MIT License.
Happy coding!