Is it a good practice to push renv folder and renv.lock file to github along with other files?
So basically, I have a project(created as a package) where I have set renv package management.
So when I push my other files to GITHUB, is it required to push renv folder and renv.lock file so that other developer who pulls the same project can use it
Yes, the project package library created by renv consists of symbolic links pointing to a global package cache so they do not get pushed to github unnecessarily (unless you explicitly isolate your project).
When another person clones your project and loads it, they get warned that the project is out of sync and they should run renv::restore() to fix it
I think you should stick to the default .gitignore file created by renv::init()(which ignores the project's private library) unless you have a specific reason for doing otherwise.
make sense thanks... But outside renv folder , there is a file created called renv.lock. So as per you, this is not included in gitignore so we need to push it? Right?
So when another developer pulls my project he can restore it? Is my understanding correct?