Create new repository (copy from other repository)

[GoogleCodeExporter]

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.

Original issue reported on code.google.com by marcomsousa on 21 Sep 2012 at 10:47

[GoogleCodeExporter]

Option 1 is a subset of issue 5.

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

Original comment by James.Mo...@gmail.com on 21 Sep 2012 at 12:25

[GoogleCodeExporter]

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-Man
ager-Workflow

Original comment by marcomsousa on 21 Sep 2012 at 2:54

[GoogleCodeExporter]

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

Original comment by James.Mo...@gmail.com on 21 Sep 2012 at 3:34

[GoogleCodeExporter]

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)

Original comment by marcomsousa on 21 Sep 2012 at 3:39

[GoogleCodeExporter]

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

Original comment by James.Mo...@gmail.com on 21 Sep 2012 at 5:29

• Changed state: Accepted
• Added labels: Milestone-1.2.0

[GoogleCodeExporter]

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.

Original comment by James.Mo...@gmail.com on 30 Sep 2012 at 3:46

[GoogleCodeExporter]

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

Original comment by James.Mo...@gmail.com on 31 Oct 2012 at 8:59

• Changed state: Queued

[GoogleCodeExporter]

v1.2.0 has been deployed.

Original comment by James.Mo...@gmail.com on 1 Jan 2013 at 1:06

• Changed state: Fixed