GimletD acts as a release manager and detaches the release workflow from CI. By doing so, it unlocks the possibility of advanced release logics and flexibility to refactor workflows.

By assuming all release related work, it adds central control to the release workflow by introducing policy based deploys and advanced authorization and security standards, while it also optimizes the GitOps repository write performance.

See the documentation.

Thank you for your interest in contributing to the Gimlet project.

Below are some of the guidelines and best practices for contributing to this repository:

If you encounter any issues or have any relevant questions, please add an issue to GitHub issues.

If you have any ideas on new features or want to improve the existing features, you can suggest it by opening a GitHub issue. Make sure to include detailed information about the feature requests, use cases, and any other information that could be helpful.]

• Fork the repository.
• Create a new branch and make your changes.
• Open a pull request with detailed commit message and reference issue number if applicable.
• A maintainer will review your pull request, and help you throughout the process.