-
Notifications
You must be signed in to change notification settings - Fork 286
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
Don't include CRAN install instructions to start #1507
Merged
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
98f71bc
don't include CRAN install instructions to start
malcolmbarrett 26bbbc7
Insert placeholder for install instructions if not yet on GitHub
jennybc 076fffe
Move TODO re: updating install instructions
jennybc b599006
Remove extra 'the'
jennybc f46ecb6
Delete another extra 'the'
jennybc ff44d61
add todo to update readme install
malcolmbarrett 4aab0bc
add to news
malcolmbarrett 1d8dd83
Merge branch 'adjust_readme_install' of https://github.com/r-lib/uset…
malcolmbarrett 233e6cf
update release snapshot
malcolmbarrett b9f2aca
Message style
jennybc 7e6b4f5
Remove more 'the'
jennybc 958b098
Use more derived data in README.md case
jennybc 712f5a0
Tweak NEWS
jennybc 8083f12
More `master` to `v1` stuff re: r-lib/actions
jennybc e9a4bec
Use new `transform` feature in testthat
jennybc File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,184 @@ | ||
# use_readme_md() has expected form for a non-GitHub package | ||
|
||
Code | ||
writeLines(read_utf8("README.md")) | ||
Output | ||
|
||
# {TESTPKG} | ||
|
||
<!-- badges: start --> | ||
<!-- badges: end --> | ||
|
||
The goal of {TESTPKG} is to ... | ||
|
||
## Installation | ||
|
||
You can install the development version of {TESTPKG} like so: | ||
|
||
``` r | ||
# FILL THIS IN! HOW CAN PEOPLE INSTALL YOUR DEV PACKAGE? | ||
``` | ||
|
||
## Example | ||
|
||
This is a basic example which shows you how to solve a common problem: | ||
|
||
``` r | ||
library({TESTPKG}) | ||
## basic example code | ||
``` | ||
|
||
|
||
# use_readme_md() has expected form for a GitHub package | ||
|
||
Code | ||
writeLines(read_utf8("README.md")) | ||
Output | ||
|
||
# {TESTPKG} | ||
|
||
<!-- badges: start --> | ||
<!-- badges: end --> | ||
|
||
The goal of {TESTPKG} is to ... | ||
|
||
## Installation | ||
|
||
You can install the development version of {TESTPKG} from [GitHub](https://github.com/) with: | ||
|
||
``` r | ||
# install.packages("devtools") | ||
devtools::install_github("OWNER/TESTPKG") | ||
``` | ||
|
||
## Example | ||
|
||
This is a basic example which shows you how to solve a common problem: | ||
|
||
``` r | ||
library({TESTPKG}) | ||
## basic example code | ||
``` | ||
|
||
|
||
# use_readme_rmd() has expected form for a non-GitHub package | ||
|
||
Code | ||
writeLines(read_utf8("README.Rmd")) | ||
Output | ||
--- | ||
output: github_document | ||
--- | ||
|
||
<!-- README.md is generated from README.Rmd. Please edit that file --> | ||
|
||
```{r, include = FALSE} | ||
knitr::opts_chunk$set( | ||
collapse = TRUE, | ||
comment = "#>", | ||
fig.path = "man/figures/README-", | ||
out.width = "100%" | ||
) | ||
``` | ||
|
||
# {TESTPKG} | ||
|
||
<!-- badges: start --> | ||
<!-- badges: end --> | ||
|
||
The goal of {TESTPKG} is to ... | ||
|
||
## Installation | ||
|
||
You can install the development version of {TESTPKG} like so: | ||
|
||
``` r | ||
# FILL THIS IN! HOW CAN PEOPLE INSTALL YOUR DEV PACKAGE? | ||
``` | ||
|
||
## Example | ||
|
||
This is a basic example which shows you how to solve a common problem: | ||
|
||
```{r example} | ||
library({TESTPKG}) | ||
## basic example code | ||
``` | ||
|
||
What is special about using `README.Rmd` instead of just `README.md`? You can include R chunks like so: | ||
|
||
```{r cars} | ||
summary(cars) | ||
``` | ||
|
||
You'll still need to render `README.Rmd` regularly, to keep `README.md` up-to-date. `devtools::build_readme()` is handy for this. You could also use GitHub Actions to re-render `README.Rmd` every time you push. An example workflow can be found here: <https://github.com/r-lib/actions/tree/v1/examples>. | ||
|
||
You can also embed plots, for example: | ||
|
||
```{r pressure, echo = FALSE} | ||
plot(pressure) | ||
``` | ||
|
||
In that case, don't forget to commit and push the resulting figure files, so they display on GitHub and CRAN. | ||
|
||
# use_readme_rmd() has expected form for a GitHub package | ||
|
||
Code | ||
writeLines(read_utf8("README.Rmd")) | ||
Output | ||
--- | ||
output: github_document | ||
--- | ||
|
||
<!-- README.md is generated from README.Rmd. Please edit that file --> | ||
|
||
```{r, include = FALSE} | ||
knitr::opts_chunk$set( | ||
collapse = TRUE, | ||
comment = "#>", | ||
fig.path = "man/figures/README-", | ||
out.width = "100%" | ||
) | ||
``` | ||
|
||
# {TESTPKG} | ||
|
||
<!-- badges: start --> | ||
<!-- badges: end --> | ||
|
||
The goal of {TESTPKG} is to ... | ||
|
||
## Installation | ||
|
||
You can install the development version of {TESTPKG} from [GitHub](https://github.com/) with: | ||
|
||
``` r | ||
# install.packages("devtools") | ||
devtools::install_github("OWNER/TESTPKG") | ||
``` | ||
|
||
## Example | ||
|
||
This is a basic example which shows you how to solve a common problem: | ||
|
||
```{r example} | ||
library({TESTPKG}) | ||
## basic example code | ||
``` | ||
|
||
What is special about using `README.Rmd` instead of just `README.md`? You can include R chunks like so: | ||
|
||
```{r cars} | ||
summary(cars) | ||
``` | ||
|
||
You'll still need to render `README.Rmd` regularly, to keep `README.md` up-to-date. `devtools::build_readme()` is handy for this. You could also use GitHub Actions to re-render `README.Rmd` every time you push. An example workflow can be found here: <https://github.com/r-lib/actions/tree/v1/examples>. | ||
|
||
You can also embed plots, for example: | ||
|
||
```{r pressure, echo = FALSE} | ||
plot(pressure) | ||
``` | ||
|
||
In that case, don't forget to commit and push the resulting figure files, so they display on GitHub and CRAN. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think one should revise the README to be (or at least include)
install.packages()
at the time of CRAN submission, because hopefully that will soon be true and that's what you want baked into the README on CRAN.