Skip to content

Revert accidental staging→main merge (86adb303) - #992

Closed
harrymove-ctrl wants to merge 1 commit into
mainfrom
harry/revert-accidental-main-merge-86adb303
Closed

harrymove-ctrl wants to merge 1 commit into
mainfrom
harry/revert-accidental-main-merge-86adb303

Conversation

@harrymove-ctrl

Copy link
Copy Markdown
Collaborator

Why

86adb303 (“dry-run”) merged staging (8fa42bc) into main by mistake via the GitHub merges API while checking conflicts for #988. It was not an intentional promote.

What

git revert -m 1 86adb303 — restores main to the pre-merge tip (first parent 0ffbacbb / #916).

Test plan

  • CI green
  • After merge, prod /health commit returns to 0ffbacbb (or prior prod tip), not 86adb303
  • Staging still healthy on 8fa42bc

This reverts commit 86adb30 (-m 1).
That merge was created by mistake via the GitHub merges API while checking
conflicts for #988; it was not an intentional promote.

Restores main to the pre-merge tip (first parent 0ffbacb / #916).
Staging tip 8fa42bc (#990) is unchanged — re-promote via a proper PR when ready.
@harrymove-ctrl

Copy link
Copy Markdown
Collaborator Author

Closing — keeping the #988 promotion on main. Staging MCP smoke already PASS on 8fa42bc / tip 86adb30; revert was only for the accidental process + "dry-run" commit message, not bad product content. Hari asked to keep the merge.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant