pr edit uses the branches merge, not pushRemote

[NLincoln]

Describe the bug

Version:

gh version 2.4.0 (2021-12-21)
https://github.com/cli/cli/releases/tag/v2.4.0

Steps to reproduce the behavior

• Open a PR
• Add the following to the repositories .git/config:

[branch "xyz-feature-branch"]
	pushRemote = origin
	remote = origin
	merge = refs/heads/main

This should indicate to git that:

• Pushes, by default, go to origin/xyz-feature-branch
• The "upstream" of this branch is origin/main

However, upon typing gh pr edit --add-reviewers I get the error message:

no pull requests found for branch "develop"

If you change the .git/config to be:

[branch "xyz-feature-branch"]
	pushRemote = origin

Then gh works.

Expected vs actual behavior

Expected: The github cli uses the pushremote, not the merge remote to determine the PR to edit
Actual: The cli seems to use the merge remote :)

Logs

❯ gh pr edit --add-reviewer redacted
no pull requests found for branch "develop"

[mislav]

Agreed, we should be paying attention to pushRemote! Duplicate of #575 (comment)