On 12/20/18 12:43 AM, Shawn McKinney wrote: > >> >> On Dec 19, 2018, at 4:16 PM, Lothar Haeger <[email protected]> >> wrote: >> >> I've already managed to link my shiny brand new Apache ID ("lhaeger") to my >> GitHub account, so a first question would be: what - if any - are the pros >> and >> cons of using gitbox vs github? > > Good question. I’ll probably use gitbox, just so I can (continue to) use my > apache credentials. Being able to commit via github is something new for us, > and requires the repo to have been moved into gitbox.apache.org, something > that hasn’t happened yet across all project repos.
For Studio, LDAP API, and server which are already on gitbox I normally use Github. Advantage is that with Github I can use my SSH keys so don't have to type in my ASF password or mess with credential helper. On a git push to either github or gitbox the changes are replicated to the other. However just yesterday when gitbox was down [1] I pushed to github but it wasn't forwarded to gitbox so I had to push again manually to gitbox later. For that I always have both remotes configured: $ git remote -v apache https://gitbox.apache.org/repos/asf/directory-server.git (fetch) apache https://gitbox.apache.org/repos/asf/directory-server.git (push) github [email protected]:apache/directory-server.git (fetch) github [email protected]:apache/directory-server.git (push) Biggest advantage of the gitbox/github integration is that we can create and accept and merge pull requests directly. Kind Regards, Stefan [1] https://status.apache.org/
