Is this still actually being discussed or has it been dropped? It would be great to know if this is considered something that will still be addressed, as whilst we have a temporary workaround we’d like to be able to commit to a process to carry this out.
We are doing something very similar to the use case @coreycoto has, and given that, it seems this is not an edge case.
Our organization is also being blocked by this. I only found out after I created an integration bot to handle fast-forwarding of pull requests to specific branches that this is an issue, and the issue didn’t ever show itself to me until I found this is what causes the “mergeable_state” field on a PR to be “blocked” for the app:
I’m off to waste time reworking my bot to use a user authentication key.
This is asenine, any updates github? this has been open for over a year, and has been “investigated” with a “reproduction case” and “failing integration test” for over 6 months.
We use an automated tool that handles releases and needs to push to master (nlm). We wanted to use protected branches since they came out but were never able to because of this issue. Definitely looking forward to a resolution!