Skip to content

feat: abort merge when there's going to be data lost during a merge - #1081

Closed
doc-han wants to merge 11 commits into
mainfrom
cli-merge-with-abort
Closed

doc-han wants to merge 11 commits into
mainfrom
cli-merge-with-abort

Conversation

@doc-han

@doc-han doc-han commented Oct 21, 2025

Copy link
Copy Markdown
Collaborator

Short Description

Checks whether all workflows from the workflow-mapping of a merge are compatible before merging. if not we then throw an error to abort the merge.

Fixes #

Implementation Details

A more detailed breakdown of the changes, including motivations (if not provided in the issue).

QA Notes

List any considerations/cases/advice for testing/QA here.

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to know!):

  • Code generation (copilot but not intellisense)
  • Learning or fact checking
  • Strategy / design
  • Optimisation / refactoring
  • Translation / spellchecking / doc gen
  • Other
  • I have not used AI

You can read more details in our Responsible AI Policy

Release branch checklist

Delete this section if this is not a release PR.

If this IS a release branch:

  • Run pnpm changeset version from root to bump versions
  • Run pnpm install
  • Commit the new version numbers
  • Run pnpm changeset tag to generate tags
  • Push tags git push --tags

Tags may need updating if commits come in after the tags are first generated.

@github-project-automation github-project-automation Bot moved this to New Issues in Core Oct 21, 2025
@doc-han
doc-han force-pushed the cli-merge-with-abort branch from 39db674 to 6b3b377 Compare October 21, 2025 14:34
@josephjclark
josephjclark changed the base branch from main to 980-sandbox-add-versioning-and-version-history-checking October 22, 2025 15:26

@josephjclark josephjclark left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good - a couple of small comments but I think this is OK. More important that we get the base logic right.

I was expecting the validation to all be in the CLI. But I guess it's OK in the Project?

Comment thread packages/cli/src/merge/command.ts Resolved
Base automatically changed from 980-sandbox-add-versioning-and-version-history-checking to release/next October 24, 2025 14:29
@josephjclark
josephjclark changed the base branch from release/next to main October 24, 2025 14:36
@github-project-automation github-project-automation Bot moved this from New Issues to Done in Core Oct 24, 2025
@josephjclark

Copy link
Copy Markdown
Collaborator

Merge got hairy so I did this in #1094

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants