[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

why, nicely explained (Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)



On Wed, Jun 08, 2016 at 03:19:09PM +0000, Felipe Sateler wrote:
> Git is not only for code hosting. It is also a tool for collaborating, 
> even with people not formally affiliated with your project.
> 
> So, say I want to contribute to a project I don't normally work in. Steps 
> in alioth:
> 
> - debcheckout project
> - hack (possibly in own branch)
> - ssh into alioth
> - alioth$ mkdir -p ~/public_git/project.git
> - alioth$ cd ~/public_git/project.git && git init --bare
> - git remote add personal\
>     git+ssh://git.debian.org/git/users/$user/project.git
> - git push -u personal $currentbranch
> - Wait some minutes for cron job to pick up your repo
> - Realize you did not edit description, nor touch the magic
>   git-daemon-export-ok file in the remote repo, do so.
> - Wait some minutes again
> - Send mail to project maintainer instructing them to pull from
>   https://anonscm.debian.org/git/users/$user/project.git
> 
> Compare with gitlab:
> 
> - go to https://gitlab.debian.org/project/project
> - click fork
> - git clone the url gitlab will tell you
> - hack
> - push
> - click "Submit Merge Request" button on the same page
> 
> If the change is small enough (ie, doc/typo fixes), you can even edit the 
> file directly in the web browser.
 
Thanks for this nice summary. It helped me understand things better.


-- 
cheers,
	Holger

Attachment: signature.asc
Description: Digital signature


Reply to: