Closed IndrajeetPatil closed 2 years ago
In light of discussion here, the scope of this workflow has changed now.
Before, we wanted to use it to make sure that:
The second was never working, and given that we protect the main branch, it never will.
So, its only job now is to make sure that the new commit/PR doesn't break the README.
@easystats/core-team Please make a note.
This means that any time you make a change to README.Rmd, you should also knit it and update README.md as well.
README.Rmd
README.md
In light of discussion here, the scope of this workflow has changed now.
Before, we wanted to use it to make sure that:
The second was never working, and given that we protect the main branch, it never will.
So, its only job now is to make sure that the new commit/PR doesn't break the README.
@easystats/core-team Please make a note.
This means that any time you make a change to
README.Rmd
, you should also knit it and updateREADME.md
as well.