Skip to content
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

Add a render-readme.yaml GH action #544

Open
jdhoffa opened this issue Feb 1, 2024 · 4 comments · Fixed by #554
Open

Add a render-readme.yaml GH action #544

jdhoffa opened this issue Feb 1, 2024 · 4 comments · Fixed by #554
Labels
upkeep maintenance, infrastructure, and similar

Comments

@jdhoffa
Copy link
Member

jdhoffa commented Feb 1, 2024

This package uses a README.Rmd style README. It is common to forget to knit this README, and risk that the README.md falls out of sync.

This is a suggestion to add a GH action to keep track of this.

Relates to RMI-PACTA/r2dii.match#444
(The action can just be copied directly from there, if you are comfortable with an action automatically pushing to your PRs.)

@jdhoffa jdhoffa added the upkeep maintenance, infrastructure, and similar label Feb 1, 2024
@MonikaFu
Copy link
Collaborator

I believe that we used this action for a while but it was causing issues, that is why we removed it (me and Mauro). We can try to re-introduce it though.

@jdhoffa
Copy link
Member Author

jdhoffa commented Feb 19, 2024

That makes sense! It was causing me headaches too, but I managed to get it to work in RMI-PACTA/r2dii.match#444

I leave it up to you, if you think it's something you may want then keep this open, otherwise feel free to close it with no action!

@MonikaFu
Copy link
Collaborator

Thanks! Let's try your solution then. Doesn't need to be for this release, though.

@jdhoffa
Copy link
Member Author

jdhoffa commented Feb 29, 2024

Reopening because apparently #554 didn't work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upkeep maintenance, infrastructure, and similar
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants