🚨 Repo PR Alert! 🚨 (Resolved!)
(Read: Whoopsie, sorry — Please stand by!)
A total of 84 PRs were inadvertently closed by an automated process which was expected to re-target them to a new default branch (main, via #4302), but instead re-targeted merely 23 of the open PRs and instead closed 84 others. (An additional 14 were not affected but had already been targeted to the main branch.)
The expectation was that the pull-request re-targeting feature would handle this when #4302 merged, but it seems it only partially succeeded (this is the automatic process referred to above). I did test this on another repository prior to doing this, so I was certainly not expecting this result!
~We have contacted GitHub Support to see if they can re-open these programmatically, otherwise we will investigate further and take action ourselves. So very sorry for PRs that were automatically closed! I'm going to leave the repository as is for the time being, but stand by for updates!
~
😭
🚨 Repo PR Alert! 🚨(Resolved!)(Read: Whoopsie, sorry — Please stand by!)A total of 84 PRs were inadvertently closed by an automated process which was expected to re-target them to a new default branch (
main, via #4302), but instead re-targeted merely 23 of the open PRs and instead closed 84 others. (An additional 14 were not affected but had already been targeted to themainbranch.)The expectation was that the pull-request re-targeting feature would handle this when #4302 merged, but it seems it only partially succeeded (this is the automatic process referred to above). I did test this on another repository prior to doing this, so I was certainly not expecting this result!
~We have contacted GitHub Support to see if they can re-open these programmatically, otherwise we will investigate further and take action ourselves. So very sorry for PRs that were automatically closed! I'm going to leave the repository as is for the time being, but stand by for updates!
~
😭