Create new repository (copy from other repository)

[gitblit]

Originally reported on Google Code with ID 137

Is nice that we can copy one repository from the local gitblit or from url. Like a fork.

We can have two options.

Create new repository -> 
1>Select the check "Fork from other location" and happear one url textbox to copy from.
2>Select the check "Fork from local" and happear one combobox with the  list of all
gitblit repository.

Reported by marcomsousa on 2012-09-21 10:47:51

[gitblit]

Option 1 is a subset of issue 301.

I'm not sure about option 2.  Perhaps as part of a personal repositories feature, which
has been considered.

Reported by James.Moger on 2012-09-21 12:25:29

[gitblit]

To do the Integration-Manager-Workflow in the git documentation, all public repos are
a copy of the "blessed repository" all branches or one branch (we can also do this
with a checkbox and combobox/textbox).

http://git-scm.com/book/en/Distributed-Git-Distributed-Workflows#Integration-Manager-Workflow

Reported by marcomsousa on 2012-09-21 14:54:57

[gitblit]

I don't know that I'm convinced Gitblit needs explicit support for forking but if I
implement personal repos, then I'll add it.

To my mind this process achieves the same goal:
git clone https://git.somewhere.com/git/blessed.git myclone
(create myclone repo in Gitblit)
git remote add gitblit https://git.somewhere.com/git/myclone.git
git push gitblit

Reported by James.Moger on 2012-09-21 15:34:18

[gitblit]

that's correct, but if the repo was 1GB in size?

You will have to clone all full repo and after send the same bits to server. (so the
traffic is the double)

Reported by marcomsousa on 2012-09-21 15:39:15

[gitblit]

Excellent.  Now that is a compelling reason to have server-side forking.  I'll put it
on the todo list.

Reported by James.Moger on 2012-09-21 17:29:57

• Status changed: Accepted
• Labels added: Milestone-1.2.0

[gitblit]

I have implemented preliminary server-side forking.  The current design is modeled after
GitHub (hands-off forking to a personal repository) so it does not take into account
your request of cloning a remote repository.  That will be considered in the next phase
- manual creation of a personal repository.

Reported by James.Moger on 2012-09-30 03:46:14

[gitblit]

The forking has been implemented on master for a while now.  The other request, clone
from a remote, is issue 301.

Reported by James.Moger on 2012-10-31 20:59:31

• Status changed: Queued

[gitblit]

v1.2.0 has been deployed.

Reported by James.Moger on 2013-01-01 01:06:25

• Status changed: Fixed