-
Notifications
You must be signed in to change notification settings - Fork 287
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
Feature request: Update version of citation files with use_version
#2081
Comments
I just did a GitHub search for If your own practices are consistent enough that you think this could be automated for your packages, it sounds like a good fit for a custom release bullet: https://usethis.r-lib.org/reference/use_release_issue.html
|
Is there any more documentation of the function? It sounds like it's just an issue that's generated, not an action that updates files - am I understanding that wrong? It can definitely be automated, cffr does it; maybe it could be a parameter that defaults to |
There's not a lot of documentation around the custom release bullets and, yes, it's a reminder to update something, not an automation of it. The best way to see examples of it would be to do a GitHub search of CRAN packages for I'm guessing that cffr can assume certain practices in the CITATION file, which then makes those files predictable and more favorable for automatic editing. |
use_version
is super convenient for updating the the version in bothDESCRIPTION
andNEWS.md
, however, one still has to manually edit theinst/CITATION
(andCITATION.cff
) file(s). It would be great ituse_version
could check whether such file(s) were present, and if they are, update the version within them.The text was updated successfully, but these errors were encountered: