git - R Studio - Cloning local repository -

I want to create a master repository on our server, so that I can clone a local version on my computer.

I am using R Studio v0.98.994.

So far, I have tried to do this:

Create a folder to stay inside the master repository. I ask this in the studio using the 'new project', and make it a GIT repository.

Then I can open another new project on my C drive, and use R Studio for clone, to open an existing project and set the URL as the location of the master project Is saying for.

However, when I make changes and I commit to my local repository (which works fine), then I get an error in the master repository, as described in this question:

So it seems that R Studio makes non-berry repository?

Now I thought, okay, I'll use GIT bash to start the repository and then connect it to R within the studio.

I do this, but c Anot then searches for a way to use that repository in R studio.

I am very new to Git, so it is entirely possible that they read one of those 'instructions' questions, in which case I am very sorry - and do somebody please me Can you point to some guidance for this situation? I have spent a good half day of one day around this error and have not managed to pull the pieces together so far :( I also apologize, it does not feel like a very repetitive question It seems that you are using Windows GIT, the local Windows machine (C: drive).

P>

Shared Reserves

If you intend to share more than one person with the same stock , You want to start an share repository. See the --shared option for more information. Note that I am not sure that having your repository on Windows machine affects the sharing option. Your repository Keep the person in two places, which makes things very easy.

Bread repositories

There is talk of separate repositories different from the discussion of sharing. If you do not intend to ever Working with files in the server (i.e. this is just going to be a place to push the changes so that they are stored safely), you can start an bare regressory in a small store Git has a database structure, but Stvik files in the directory.

A standard Git repository is designated with a written folder .git . This .git folder contains all the different data structures that one uses to track the change of gates, an unmatched repository essentially containing only the content of .git Is the folder.

The good thing about a bare regression is that no one can work in the repository (because a working directory, just the database) it means that no one can log in in S Has: Edit yourself and the repository. Instead, they have to clone the repository, then put their changes back into the original. There is a good article on why this is ideal.

Note that shared repo and rogue repo are not dependent or mutually exclusive. As a general practice, if you have a "server repo" from which you pull and on which you push, you should tell it, whether the project is shared.

A non-shared workflow

As it is not clear whether you are sharing or not sharing, and you are on a Windows environment, from a shared perspective Do not know, I want to give you a simple example. Using GIT-bash, where you can place the directory on the S: you have your repositories. Then, use git init with bare options, as it is described by initializing the link above to initialize a bare registrar, navigate to where you want your repository to remain on C, And then git clone to get a working copy.

Add a README file or something so that you commit to your initial commitment, and then commit to push your changes into S: repository and git push master master once All this is done, then the RSTUDO GIT project is started. RStudio should be converted to its current configuration and things should work