Best practices for sharing options() configurations

General
1

With the recent updates to the blogdown package I am utilizing some of the package configuration options to customize how blogdown interacts with Hugo. For example, I prefer all my RMarkdown files render to a Markdown format as opposed to HTML, so I added

options(blogdown.method = "markdown")

to my .Rprofile. Which works great when I am developing my site locally, but when I try to work with collaborators via Git and GitHub, I specifically do not track changes in .Rprofile because it also contains API tokens and other sensitive information. But if my collaborators do not have the same options() configuration then their version of the site will not render as intended.

Does anyone have recommendations for how to best share these types of options() as part of project management without needing to share the complete .Rprofile?

2

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.