Skip to content

Conversation

cofinoa
Copy link
Collaborator

@cofinoa cofinoa commented Oct 1, 2025

Reverts #73

@JonathanGregory
Copy link
Contributor

Thanks, @cofinoa. Shall I merge it?

@cofinoa
Copy link
Collaborator Author

cofinoa commented Oct 6, 2025

Hi @JonathanGregory,

Short answer: yes, we can merge this revert.

Long answer:

Just to clarify the plan and context for this revert (#612):

Since #73 was merged by mistake, this revert is simply a corrective step.

Once this revert is merged, I’ll open a new PR re-applying #73 (with the same content) so that it follows the proper process.

When re-applying it, I’ll cherry-pick the original commits so that the original authorship and commit history are preserved.

For reference, the commits from #73 are:

Please merge this when you’re happy with it. After that, I’ll proceed to re-apply #73 properly.

@JonathanGregory
Copy link
Contributor

Thanks for doing this.

@JonathanGregory JonathanGregory merged commit 52eef68 into main Oct 6, 2025
1 check passed
@cofinoa cofinoa deleted the revert-73-patch-1 branch October 6, 2025 16:52
cofinoa added a commit that referenced this pull request Oct 6, 2025
This commit unintentionally landed on upstream/main.
Reverting to restore main to the correct state.
Refs: #73, #612

This reverts commit 98e88a4.
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.

2 participants