-
Notifications
You must be signed in to change notification settings - Fork 761
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
A use_news() function #957
Comments
It is imo unclear what the best practice is.
Personally I like NEWS.md. In fact recently (wch/r-source@e7cf1f0) NEWS.md is picked up by CRAN. Incidentally inst/NEWS.md is also picked up, which is a pity, because I specifically put NEWs.md in inst/ so that CRAN does not bother with them.... CRAN uses Pandoc to format Markdown, which is unfortunate, because GitHub uses a different parser, and you often end up with an MD file that is fine on GitHub, but gives warnings or errors on CRAN. And then you get emails from CRAN. |
Btw. here is a recent discussion about NEWS.md: http://r.789695.n4.nabble.com/NEWS-md-support-on-CRAN-td4707539.html |
The current way in the R Extensions manual is NEWS so we can start with that first? We can then converge on markdown as the R versions move towards it. |
I only use |
@gaborcsardi have there been any updates to |
@hadley It is a problem in r-release I think, but not in r-devel. Unless there was a change since wch/r-source@e7cf1f0 ... There was no change it seems: https://github.com/wch/r-source/commits/e7cf1f06c0cdf439eca9d561b84316a44089e142/src/library/tools/R/check.R So yes,
|
So that means |
YEs, I think so. (Except for the pandoc failures. :) |
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/ |
It would be very handy if there was a function that created the NEWS file, and ideally contained a "best practice" example
Apologies if this has already been requested and declined, could only find #105
The text was updated successfully, but these errors were encountered: