-
Notifications
You must be signed in to change notification settings - Fork 754
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
Updating the Description file Date field? #1327
Comments
The |
I was not aware of that, thanks for the tip! |
I agree. It would be nice for the Date to be automatically loaded into the DESCRIPTION file by default. That way (for example)
The current citation for the
This will most likely generate nagging comments from journal reviewers when citing R packages in manuscripts/publications. |
@melindahiggins2000 That behavior will only happen when installing the package with citation("tidyr")
#>
#> To cite package 'tidyr' in publications use:
#>
#> Hadley Wickham (2016). tidyr: Easily Tidy Data with `spread()`
#> and `gather()` Functions. R package version 0.6.0.
#> https://CRAN.R-project.org/package=tidyr
#>
#> A BibTeX entry for LaTeX users is
#>
#> @Manual{,
#> title = {tidyr: Easily Tidy Data with `spread()` and `gather()` Functions},
#> author = {Hadley Wickham},
#> year = {2016},
#> note = {R package version 0.6.0},
#> url = {https://CRAN.R-project.org/package=tidyr},
#> } we could add this same field to the package description when we install it from GitHub, which would fix the behavior you describe. |
Ahh good point - I see now the difference in the CRAN vs development Github versions. I just think in general it is good practice to track the date of the current version in use and when cited. Thank you for the clarification. |
@jimhester If I'm understanding correctly, this is not implemented yet
I think that can actually be very helpful, not just for
|
Adding to what has been mentioned above, I believe it would be useful for the date field to be updated automatically (specifically, for use with |
Why build date, rather than timestamp of the commit from which it was built? I'd compared that with the publication date of an article vs. the timestamp of the publisher-generated PDF that I download. Also: can the version be mapped back to a git commit in each case? When using the GitHub-Zenodo integration and being stringent about release tagging, it always can be, can't it? |
This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/ |
Is it possible to add an option when building/checking a package to automatically update the Date field in the description file? An outdated Date fields seems to be a common mistake in the submission of packages to CRAN (I know I forget to do so often); adding this option would probably go a long way in reducing that error.
The text was updated successfully, but these errors were encountered: