Skip to main content
added 95 characters in body
Source Link

I am new to Git and am learning as much as I can about it.

The latest thing I would like to know is how to approach this problem: I have a single folder (R) that I initially set up as a Git repository.

Since setting R up, it now contains several projects and it is now the case that I have several branches, each reflecting a different project and I don't like it because it feels untidy and disorganised.

As such, I am thinking that the best way to approach the problem might be to create a new repository for each project. (Note that each project is a sub-directory of R.)

However, I know that creating a new repository means starting afresh (i.e. no branches or previous commits). Second - I'm sure the answer is yes - but I wonder if I can copy across a branch from R where I used to track changes previously so that I can continue with the new project as a repository as opposed to being a sub-directory of another repository.

So I have two questions:

  1. Is it a good idea to split each project out into its own repository? (If so, will this affect the overall structure of R? The idea is that I stop using R as a repository and instead use R\Project1 and R\Project2, etc, as separate repositories.)
  2. Is there a way to copy a branch from R into the new repository?

Note: I am the sole developer/user of these files at present - no others are involved.

I am new to Git and am learning as much as I can about it.

The latest thing I would like to know is how to approach this problem: I have a single folder (R) that I initially set up as a Git repository.

Since setting R up, it now contains several projects and it is now the case that I have several branches, each reflecting a different project and I don't like it because it feels untidy and disorganised.

As such, I am thinking that the best way to approach the problem might be to create a new repository for each project. (Note that each project is a sub-directory of R.)

However, I know that creating a new repository means starting afresh (i.e. no branches or previous commits). Second - I'm sure the answer is yes - but I wonder if I can copy across a branch from R where I used to track changes previously so that I can continue with the new project as a repository as opposed to being a sub-directory of another repository.

So I have two questions:

  1. Is it a good idea to split each project out into its own repository? (If so, will this affect the overall structure of R? The idea is that I stop using R as a repository and instead use R\Project1 and R\Project2, etc, as separate repositories.)
  2. Is there a way to copy a branch from R into the new repository?

I am new to Git and am learning as much as I can about it.

The latest thing I would like to know is how to approach this problem: I have a single folder (R) that I initially set up as a Git repository.

Since setting R up, it now contains several projects and it is now the case that I have several branches, each reflecting a different project and I don't like it because it feels untidy and disorganised.

As such, I am thinking that the best way to approach the problem might be to create a new repository for each project. (Note that each project is a sub-directory of R.)

However, I know that creating a new repository means starting afresh (i.e. no branches or previous commits). Second - I'm sure the answer is yes - but I wonder if I can copy across a branch from R where I used to track changes previously so that I can continue with the new project as a repository as opposed to being a sub-directory of another repository.

So I have two questions:

  1. Is it a good idea to split each project out into its own repository? (If so, will this affect the overall structure of R? The idea is that I stop using R as a repository and instead use R\Project1 and R\Project2, etc, as separate repositories.)
  2. Is there a way to copy a branch from R into the new repository?

Note: I am the sole developer/user of these files at present - no others are involved.

deleted 2 characters in body
Source Link

I am new to Git and am learning as much as a I can about it.

The latest thing I would like to know is how to approach this problem: I have a single folder (R) that I initially set up as a Git repository.

Since setting R up, it now contains several projects and it is now the case that I have several branches, each reflecting a different project and I don't like it because it feels untidy and disorganised.

As such, I am thinking that the best way to approach the problem might be to create a new repository for each project. (Note that each project is a sub-directory of R.)

However, I know that creating a new repository means starting afresh (i.e. no branches or previous commits). Second - I'm sure the answer is yes - but I wonder if I can copy across a branch from R where I used to track changes previously so that I can continue with the new project as a repository as opposed to being a sub-directory of another repository.

So I have two questions:

  1. Is it a good idea to split each project out into its own repository? (If so, will this affect the overall structure of R? The idea is that I stop using R as a repository and instead use R\Project1 and R\Project2, etc, as separate repositories.)
  2. Is there a way to copy a branch from R into the new repository?

I am new to Git and am learning as much as a I can about it.

The latest thing I would like to know is how to approach this problem: I have a single folder (R) that I initially set up as a Git repository.

Since setting R up, it now contains several projects and it is now the case that I have several branches, each reflecting a different project and I don't like it because it feels untidy and disorganised.

As such, I am thinking that the best way to approach the problem might be to create a new repository for each project. (Note that each project is a sub-directory of R.)

However, I know that creating a new repository means starting afresh (i.e. no branches or previous commits). Second - I'm sure the answer is yes - but I wonder if I can copy across a branch from R where I used to track changes previously so that I can continue with the new project as a repository as opposed to being a sub-directory of another repository.

So I have two questions:

  1. Is it a good idea to split each project out into its own repository? (If so, will this affect the overall structure of R? The idea is that I stop using R as a repository and instead use R\Project1 and R\Project2, etc, as separate repositories.)
  2. Is there a way to copy a branch from R into the new repository?

I am new to Git and am learning as much as I can about it.

The latest thing I would like to know is how to approach this problem: I have a single folder (R) that I initially set up as a Git repository.

Since setting R up, it now contains several projects and it is now the case that I have several branches, each reflecting a different project and I don't like it because it feels untidy and disorganised.

As such, I am thinking that the best way to approach the problem might be to create a new repository for each project. (Note that each project is a sub-directory of R.)

However, I know that creating a new repository means starting afresh (i.e. no branches or previous commits). Second - I'm sure the answer is yes - but I wonder if I can copy across a branch from R where I used to track changes previously so that I can continue with the new project as a repository as opposed to being a sub-directory of another repository.

So I have two questions:

  1. Is it a good idea to split each project out into its own repository? (If so, will this affect the overall structure of R? The idea is that I stop using R as a repository and instead use R\Project1 and R\Project2, etc, as separate repositories.)
  2. Is there a way to copy a branch from R into the new repository?
Source Link

It is good practice for each project (within a directory) to be split out into its own repository?

I am new to Git and am learning as much as a I can about it.

The latest thing I would like to know is how to approach this problem: I have a single folder (R) that I initially set up as a Git repository.

Since setting R up, it now contains several projects and it is now the case that I have several branches, each reflecting a different project and I don't like it because it feels untidy and disorganised.

As such, I am thinking that the best way to approach the problem might be to create a new repository for each project. (Note that each project is a sub-directory of R.)

However, I know that creating a new repository means starting afresh (i.e. no branches or previous commits). Second - I'm sure the answer is yes - but I wonder if I can copy across a branch from R where I used to track changes previously so that I can continue with the new project as a repository as opposed to being a sub-directory of another repository.

So I have two questions:

  1. Is it a good idea to split each project out into its own repository? (If so, will this affect the overall structure of R? The idea is that I stop using R as a repository and instead use R\Project1 and R\Project2, etc, as separate repositories.)
  2. Is there a way to copy a branch from R into the new repository?