You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some learners are getting a .Rproj.user directory in their project root and/or code/. This causes a bunch of unnecessary things to show up when they git add .
A couple of thoughts...
Don't use git add ., rather, be specific about what files to add - git add file1 file2 etc.
Do git status see that there's a .Rproj.user directory and introduce .gitignore and add .Rproj.user to that
I think both are probably good practices to teach people. There's a potential problem they could run into in their future where they accidentally commit a large file and then try to push it. Then Bad Things Happen. By being specific about git add they can reduce the risk of this.
The text was updated successfully, but these errors were encountered:
I like the idea of introducing the .gitignore file. Existing projects they clone will probably have one, and it might cause confusion if certain files don't show up in the staging area.
It is an application of the wildcards covered in the bash section!
Some learners are getting a
.Rproj.user
directory in their project root and/orcode/
. This causes a bunch of unnecessary things to show up when theygit add .
A couple of thoughts...
git add .
, rather, be specific about what files to add -git add file1 file2 etc.
git status
see that there's a.Rproj.user
directory and introduce.gitignore
and add.Rproj.user
to thatI think both are probably good practices to teach people. There's a potential problem they could run into in their future where they accidentally commit a large file and then try to push it. Then Bad Things Happen. By being specific about
git add
they can reduce the risk of this.The text was updated successfully, but these errors were encountered: