Shawn Sörbom <sh...@sorbom.com> writes: > Thats why I wanted to use gbp, I was afraid of missing details.
It's really not that bad: 1. make sure your repo knows about its github "origin" 2. push each branch (if you used push -u once, then for subsequent pushes you can mit the "origin master") 3. push all tags (if you are paranoid, you can check the git push'es beforehand with --dry-run) There is not more to it, now you have a complete remote copy. > Ideally, I would have preferred to use Debian alioth servers, but after > reading the FAQ, I didn't think my package qualified. > Thank you both for your replies. > --Shawn > On Sunday, September 21, 2014 10:44:19 Felix Natter wrote: >> Daniel Lintott <dan...@serverb.co.uk> writes: >> > So the workaround for this is to simply create an empty repo via the >> > GitHub web interface and push to that. So if you already have you >> > package prepared using Git: >> > >> > 1. git remote add origin g...@github.com:user/repo.git >> > 2. git push -u origin master >> > >> > In addition you'll need to push any additional branches (pristine-tar, >> > upstream) to GitHub. >> >> You also need to push tags: >> http://git-scm.com/book/en/Git-Basics-Tagging#Sharing-Tags >> >> Best Regards, > Best Regards, -- Felix Natter -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/878ulbv5mc....@bitburger.home.felix
