[BUG]: GitHub API idiosyncrasies

[claudioandre-br]

Which version of the application are you using?

1.9J1+2404, latest bleeding

Description of the bug

The GitHub API is strange:

If you run the API within a PR review, the mergeStateStatus will not be clean (even when it is clean). E.g.:

• Approvals: 1
• Everything else is ok (confirmed using GitHub GUI).

mergeStateStatus: {"createdBy":[],"currentBranch":{"mergeStateStatus":"UNSTABLE"},"needsReview":[]}

I'll probably remove this validation from our scripts.

Steps To Reproduce

No response

Your execution environment

No response

[claudioandre-br]

GitHub's security model is a bit confusing. If I'm interacting with a PR of a fork, I have the rights that the author of the fork has. I understand the motivation, but when I'm myself?

What I see in the GUI is different from what the CLI shows me. It's hard to think clearly.

[claudioandre-br]

See also #637 (comment)