Closed Bug 1282879 Opened 9 years ago Closed 9 years ago

Move releases/gecko.git to github

Categories

(Developer Services :: Git, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: hwine, Assigned: hwine)

References

Details

With the decomission of git.mozilla.org, we need a new home for the official partner facing version of gecko used by the b2g project. (This is a subset, with different branch names, of the mozilla/gecko-dev repo already on github. The shas are equivalent.)
I created a new team within the mozilla-b2g organization on github: https://github.com/orgs/mozilla-b2g/teams/b2g-archival The team will be the owner of: https://github.com/mozilla-b2g/gecko-partner which is an import of https://git.mozilla.org/releases/gecko.git The import is currently underway
so, import failed (pack too large), so had to mirror to laptop git clone --mirror https://git.mozilla.org/releases/gecko.git cd gecko.git git remote add downstream git remote add origin git@github.com:mozilla-b2g/gecko-partner.git Then push in pieces[1]: git config remote.downstream.mirror false git push downstream 626da15:refs/heads/master git push downstream 98ab079:master git push downstream 329e61a:master git push downstream 6aa40ed:master And finally all the rest: git config remote.downstream.mirror true git push downstream [1] https://stackoverflow.com/questions/15125862/github-remote-push-pack-size-exceeded
manually protected branches, as API funky atm.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.