-
Notifications
You must be signed in to change notification settings - Fork 60
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
Describe current maintenance posture #421
Conversation
I am expecting to see some sort of a bullet list appear in the new section and #186 will be on it. As it stands, the reason that this PR closes that issue is very implicit (vs. explicit). |
Co-authored-by: Jennifer (Jenny) Bryan <[email protected]>
The main / initial comment still needs to gain a bunch of "Closes #(some issue or PR number)". But otherwise, I entrust this to your hands. |
I moved the "closes" statements into the initial comment. |
@jennybc I'm not able to merge this probably because it was moved to a new org |
Just to be clear: @sbearrows you'd like me to merge this? |
@jennybc Yes I'm ready to merge it, but also I think we need to change my permissions again since I'm blocked from merging. |
@sbearrows Your permissions look correct. Perhaps this particular PR is weird, since I believe it pre-dated moving vroom from r-lib to tidyverse? I merged this and we'll just have to see if your inability to merge persists and dig further, if necessary. |
@jennybc Oh that might explain it. Alright, thanks for merging! |
Closes #186, closes #151, closes #250, closes tidyverse/readr#1316