Git migration - github vs code.gnucash.org

[Derek Atkins]

John Ralls <jralls at ceridwen.us> writes:

> Why can't we set up commit hooks on each that immediately push to the
> other? Yes, there's a small chance of a conflict if two people push
> changes of the same file to each repository at the same moment, but
> the team is so small that that likelihood is infinitesimal.

My main concern is that code.gnucash.org winds up with changes that
weren't pushed by an 'authorized' developer.

I agree we can and should set up a post-commit hook that would push the
changes to github, as well as a cron job to perform a push periodically
"just in case".

> Otherwise, I don't see this as a big deal. Having multiple remotes in
> a local repo has its uses. I maintain two repos for my gtk-osx
> projects, one on Github and one at git.gnome.org. The latter is the
> "official" one, but it is indeed helpful to be able to work with
> contributors on Github.  Unless the change is truly trivial and
> obviously correct, I don't use Github's merge facility on pull
> requests, I pull in the patch and test it, then push it back to both
> repos. I also keep a personal Gnucash repo on Github. It's useful for
> feature branches (which I rebase from time to time, be warned!),
> giving me an offsite backup and anyone interested a look at what I'm
> up to.
>
> Regards,
> John Ralls

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available