Add configuration for selecting specific dangerous change types to fail on#8175
Add configuration for selecting specific dangerous change types to fail on#8175jdolle wants to merge 10 commits into
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces granular configuration for failing dangerous change types on targets, adding database columns, GraphQL schema updates, and a frontend form to select specific dangerous changes. The review feedback focuses on simplifying a complex SQL update query, adding proper error handling with toast notifications on the frontend form submission to prevent misleading success states, improving type safety in Zod and Yup schemas, resolving conflicting CSS classes on disabled buttons, and using environment-agnostic types for timers.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
🐋 This PR was built and pushed to the following Docker images: Targets: Platforms: Image Tags: |
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
1 participant
Background
Dangerous changes can be situational based on a team's accepted risk and deployment process.
Description
This introduces a new configuration option which allows selecting individual change types.
fail-dangerous-preview.mp4