-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolved: 84 pull-requests inadvertently and mistakenly closed! #4304
Labels
Comments
abernix
added
πͺ² bug
π« in-progress
β blocking
Prevents production or dev due to perf, bug, build error, etc..
π§π·ββοΈπ·ββοΈπ§ in triage
Issue currently being triaged
labels
Jun 24, 2020
This was referenced Jun 24, 2020
Closed
This was referenced Jun 24, 2020
Ooooooooof. Sending good vibes lol |
abernix
changed the title
π¨ Note! 84 pull-requests inadvertently and mistakenly closed!
Resolved: 84 pull-requests inadvertently and mistakenly closed!
Jun 25, 2020
abernix
removed
β blocking
Prevents production or dev due to perf, bug, build error, etc..
π« in-progress
π§π·ββοΈπ·ββοΈπ§ in triage
Issue currently being triaged
labels
Jun 25, 2020
β¨ Hopefully all back to normal! There were 5 PRs that couldn't be re-opened either because:
I have manually fixed all of them, or just maintained the already-re-opened PRs. For posterity's sake:
|
This was referenced Jun 25, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
π¨ 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 themain
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!
~
π
The text was updated successfully, but these errors were encountered: