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
use_tidy_upkeep_issue()
#1416
Comments
More ideas:
|
What do you think of this presentation? I always lean towards minimal, but maybe it's worth being more verbose? Pre-history
2020
2021
Evergreen
|
I like this proposed organisation. Should we add something about spelling? I confess I'm pretty foggy on what exactly maintaining WORDLIST buys for us and yet I keep doing it in many packages and I don't get bugged about spelling by CRAN 🤷♀️ |
Another change I make when I return to something is renaming |
I think spelling needs to emerge as more a standard; I've added |
Maybe call this something like |
|
another checkbox could be to update artisanal deprecation messages to use |
I think we should try and get this into this release. I’m happy to take a first pass when I’m back. |
For the purposes of discussion. Fixes #1416.
For the purposes of discussion. Fixes #1416.
* First stab at use_tidy_upkeep_issue() For the purposes of discussion. Fixes #1416. * Update R/tidy-upkeep.R * Lots of little changes that GitHub's "batch commit" was refusing to let me make via the browser * Try to determine oldrel-4 dynamically * Update snapshot * Rename the issue * Add NEWS bullet * Add more hints and links Co-authored-by: Jennifer (Jenny) Bryan <jenny.f.bryan@gmail.com>
Create an issue to bring your package up to spec with latest changes. Would divide into sections with dates (maybe just years?) so you can choose how far to go back (and some should be re-run regularly).
Initial ideas:
use_tidy_description()
+devtools::document()
use_tidy_github_actions()
cran-comments.md
devtools::document()
for very old. Maybe check that uses md?The text was updated successfully, but these errors were encountered: