Closed ateucher closed 1 year ago
One meta point that could possibly be brought out is some of the why. When your maintenance of something is very sporadic, there's the potential for a lot of friction (and dread/procrastination) when you return to a package after a long gap and have to get re-oriented to its idiosyncrasies. Making the occasional pass through (almost) everything, looking for opportunities to adopt current, shared practices can make it easier to dip in and out of different packages.
Part of my point is that this isn't really or only about good practices vs. bad or high quality vs. low. There's some value that comes simply from standardization.
@jennybc This is a great point - I added a paragraph in the intro, using a lot of your phrasing.
Do you want to actually show an example of what
use_upkeep_issue()
does?
Example added at the bottom - what do you think?
A post describing tidyverse Spring Cleaning and the new public
usethis::use_upkeep_issue()
.Preview: https://deploy-preview-635--tidyverse-org.netlify.app/blog/2023/06/spring-cleaning-2023/
I'm looking for a better image...
I'm happy to take feedback here on the post, and in the PR for
use_upkeep_issue()