-
Notifications
You must be signed in to change notification settings - Fork 8
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
Cleanup ignore files #150
Cleanup ignore files #150
Conversation
Are you sure that |
I'm not aware of a single case where these directories are created under the source package from my past experience, that's why I think these rules should be removed. I wonder if the original template author @elong0527 can provide a positive example. If not, we should remove them. Apparently, |
We can remove them. Worst-case scenario we add them back
It used to happen to my packages all the time when using roxygen2/devtools/pkgdown to document and build the package. It may have been fixed (I wouldn't have noticed since I started ignoring them), but I couldn't find any documentation for this. There are 6k+ GitHub repos that include https://github.com/search?q=path%3A.Rbuildignore%20Meta&type=code |
Found it: |
Thanks for finding it! I was frustrated that I couldn't find the source. I thought it was either
Let's not worry about it for now. If it becomes a nuisance in the future, we can add it back then |
And since I was curious, I investigated why this hasn't been addressed. Deleting these empty directories was added to |
Wow, I guess if devtools has a designated output directory like |
This PR cleans up
.gitignore
and.Rbuildignore
by removing the superfluous rules and reordering the lists.