Rollback Merge Feature#1
Conversation
This commit introduces the ability to rollback a previously merged Proposed Change. A new GraphQL mutation `CoreProposedChangeRollback` is added, which triggers a Prefect flow `rollback_proposed_change`. This flow: 1. Identifies the latest frozen diff associated with the merge. 2. Creates a new branch named `revert-<id>` from `main`. 3. Inverts the diff actions (ADDED to REMOVED, REMOVED to ADDED, UPDATED to UPDATED with previous values). 4. Detects conflicts if nodes have been modified or deleted since the original merge. 5. Applies the inverted diff to the revert branch. The core diff inversion logic is implemented in `invert_enriched_diff` and verified with unit tests. The revert branch can then be reviewed and merged using the standard Proposed Change workflow. Co-authored-by: targuan <4534767+targuan@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Implement rollback a merge feature for Proposed Changes.
PR created automatically by Jules for task 17404230459133074093 started by @targuan