I'm sorry for being so vague, but until I learn what the lingo is, I'll have to use vague terms.
Besides being the TFS Administrator at work, I am also trying to get us moved to Git. Currently, we're using Azure DevOps Services (ADS). I'm trying to get a team with data analysts in it, setup with Git in ADS. They all use RStudio. I have no experience with R. And I certainly don't have RStudio installed on my PC/laptop, nor am I ever likely to get RStudio installed. What I need to know is a 10,000 ft. level understanding of RStudio. I want to have a common language with which I can talk with them.
However, working with the first person (Bill) I've set up their first Git repo in ADS.
I know that RStudio can work with Git - which is the reason that group wants to work with Git.
So far, I've helped two people get started using Git with ADS. Yesterday I helped the second person get started. Her name is Chelsea. She spent some time showing me their current R code storage. I'll describe it here. That whole team has been storing their R code on a network share called L:. They have folders in which they put "whatevers". This is one of the first places where my ignorance comes into play. I don't know what those things are. If this were Visual Studio, then those folders would either be a solution with one or more projects, or a project that's a part of a Visual Studio solution. I don't know what they're called in RStudio, so I'm calling them "whatever". Chelsea said that each folder is a collection of R code related to generating some reports, doing data analysis etc on one thing. (Man, it is so frustrating not knowing the vernacular!) And since they've been doing this for years, they have a large collection of folders with long names using ending in something like "Vn", as in V1, V5, V12. That means version 1 of that "thing", version 5 of that "thing" and version 12 of that "thing". So, are these whatevers all something like Visual Studio solutions/projects? I'm trying to figure out how this stuff can all be stored in a Git repository or Git repositories. What would make sense to them.
You can see the problem they're facing. For however long they've been doing this, they're in the habit of storing all the code that they collaboratively work on, in this L: network share. (I can just imagine the many times they've had conflicts as two or more people are working on the same .R file at the same time!) In fact, Chelsea really had an extremely hard time getting her mind around the idea that she should clone the repo to her machine. She really wanted to clone the repo into one of those's whatevers on the L: drive. I told her that would only seriously cause them all sorts of problems, because all of them would try to clone that same repo into the same folder on their L: network drive. And now I'm wondering if Bill has already done that. I don't have any permissions to that L: drive, so I can't look for the hidden .git folder. Since RStudio works with Git, it must know how to handle local Git repos.
So, would someone please introduce me to the terms used by users of RStudio to handle working with these whatevers. How does RStudio handle working with Git? I'm assuming that RStudio will handle some of the complexities of working with Git, such as it wouldn't reveal that a modified file is probably unstaged so the user must first stage it, then commit it, before pushing it to remote. These are all concepts I'm comfortable with. Chelsea was ready to run for the hills when I walked her through it using the command prompt.