Thanks for the feature request! Agreed that this would be useful, but I do not think there is an API to revert a merged PR. Until then, we cannot act on adding this to CLI.

In the meantime, you can use gh pr view to determine the merge commit for a PR and use git locally to revert that merge commit:

gh pr view PRNUM --json mergeCommit -q .mergeCommit.oid

There's a revertResourcePath attribute in the pullrequest Object in the GraphQL API. Unsure if that's useful for request, but worth looking at.

@azizshamim @mislav Any chance there has been any progress here?

There's a revertResourcePath attribute in the pullrequest Object in the GraphQL API. Unsure if that's useful for request, but worth looking at.

This URL is for use in the browser; the best the CLI could do is link to it.

One team is migrating from Gerrit and want to mimic some of the capabilities that Gerrit has. Gerrit has topics which are essentially multi-repo PRs. GitHub PRs are scoped to a single repo.

What they are planning to do is link a set of PRs (to simulate the topic construct). I think this request comes from their commit process - if they approve a topic, they will merge the set of PRs - but if something fails, they want to be able to revert the merge.

Update: the platform team just shipped a new API to revert a PR with:

mutation ($pr: ID!, $asDraft: Boolean = false, $title: String, $body: String) {
	revertPullRequest(
		input: {
			title: $title,
			body: $body,
			draft: $asDraft,
			pullRequestId: $pr,
		}
	) {
		revertPullRequest {
			url
		}
	}
}

You can already use this as so:

# reads the query from a file:
gh api graphql -F [email protected] -f 'pr=<PR-ID>'

How should we expose this as a command in gh?

1. gh pr revert <PR>
2. gh pr merge --undo <PR> (sort of like gh pr ready --undo)

I feel like gh pr revert <PR> makes more sense intuitively, as in the web UI 'revert' is shown separately akin to how 'close' is shown separately.

When you revert a PR, you're not inherently "undoing" the merge, you're rather making a new change that reverts the commit itself.
gh pr merge --undo might imply to some people that it will undo the state of the pull request / reopen it and so on. It could also be understood to mean restoring the branch to it's former state, as if you had force pushed an older commit back to entirely get rid of the commit history / the fact it was ever merged.

@5HT2: that's a good point. A new command revert it is then 👍

@mislav How does work prioritization work for gh cli. I noticed the help wanted but haven't contributed to this repo before.

Work prioritization looks like this: if something is tagged help wanted, that means that there should be enough information in the thread for an outside contributor to pick up the feature and produce a pull request. https://github.com/cli/cli/blob/trunk/.github/CONTRIBUTING.md

Eventually, our team might also pick up this work, but before we manage to get to it, anyone is welcome to!

What's needed to help the PR progress to being reviewed and (hopefully) merged?

I'm pretty interested in using this functionality after trying out the GraphQL approach with some success.