git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Pushing to GitHub doesn't push all branches

From
Graeme Geldenhuys <graemeg@gmail.com>
Date
Jul 13, 2009, 08:12 UTC
Message-ID
<h3eqap$cov$1@ger.gmane.org>
In-Reply-To
<4A57639D.4020305@drmicha.warpmail.net>
Michael J Gruber wrote:
> 
> Please don't! That's what we're here for ;)
:) Thanks.
> git for-each-ref --shell --format="git push -f origin :%(refname)"
> refs/remotes/|while read line; do eval $line;done

OK, done this. 'git ls-remote github' doesn't show any remotes/* references anymore.

Oh by the way, I followed your advice and renamed 'origin' to 'github' so it makes a bit more sense. I used the following command:

   $ git remote rename origin github
> 
> git config remote.origin.push '+refs/remotes/*:refs/heads/*'

OK, I've done this, but I'm not 100% sure what this means. This is what I think (from reading various git help and users guide). Any branches I have which track remote references (from svn repository) will be pushed to github as various head references (normal branches). Is this correct?

On our server, which contain the svn cloned repository and the one that is only used for syncing svn -> our server -> github, I had to add a new commit which represents the svn-ignore meta data to a .gitignore file. I noticed I had to manually to a 'git checkout master' & 'git merge remotes/trunk' to pull in new updates. I thin pushed that to github.

So what is my twice hourly cron script supposed to look like? Is the following still ok?

========[ script executed by cron every 30 minutes ]============ #!/bin/sh GIT="/usr/local/bin/git"

# FPC repository cd /mnt/samba/git/fpc.git/ $GIT checkout master $GIT svn fetch $GIT gc --auto $GIT push github master ==============================

Or do I need to add a new line after '$GIT svn fetch' that does a merge.

============================== $GIT svn fetch $GIT merge remotes/trunk ... push to github ==============================

Also what do I do with the other branch I want to track. It's called remotes/fixes_2_2.

I believe I need to first create a local branch.
   git branch --track fixes_2_2 remotes/fixes_2_2

What do I need to modify in my cron script to keep both the master & fixes_2_2 branches in sync with SubVersion and push both to GitHub. I want Github to show two branches: master & fixes_2_2

Regards,
   - Graeme -
-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://opensoft.homeip.net/fpgui/
Previous: Michael J GruberNext: Michael J Gruber
Message 6 of 8 in “Pushing to GitHub doesn't push all branches”
  1. Graeme GeldenhuysJul 10, 2009
  2. Michael J GruberJul 10, 2009
  3. Michael J GruberJul 10, 2009
  4. Graeme GeldenhuysJul 10, 2009
  5. Michael J GruberJul 10, 2009
  6. Graeme GeldenhuysJul 13, 2009
  7. Michael J GruberJul 13, 2009
  8. Graeme GeldenhuysJul 13, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.