> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/guides/value-proposition/quality-use-cases/governance-and-quality-gates.md). # Governance & Quality Gates This section explores how SeaLights empowers Governance & Quality Gates. SeaLights establishes clear quality benchmarks and integrates them as automated checkpoints throughout the development workflow. This ensures code changes meet quality standards before reaching production, minimizing risks and fostering a culture of continuous improvement. * [Governance & Quality Gates - Overview](#governance-and-quality-gates-overview) * [Quality Gates for Release](#quality-gates-for-release) * [Impact of Testing Strategies & Git Flows](#impact-of-testing-strategies-and-git-flows) * [Manual vs. Automatic Quality Gates](#manual-vs.-automatic-quality-gates) *** ### Governance & Quality Gates - Overview {% file src="/files/sOxSqIRDeNcnyWLaatgf" %} Video is coming soon... ### Quality Gates for Release Video is coming soon... ### Impact of Testing Strategies & Git Flows Video is coming soon... ### Manual vs. Automatic Quality Gates Video is coming soon... --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sealights.io/knowledgebase/guides/value-proposition/quality-use-cases/governance-and-quality-gates.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.