On Fri, Mar 13, 2015 at 02:18:36PM +0100, Christian Brabandt wrote: > On Fr, 13 Mär 2015, guyzmo wrote: > > > another feature that makes working with pull requests less painful, it's > > that now you can get them from their own feature branche, by adding the > > following to the github remote: > > fetch = +refs/pull/*/head:refs/remotes/origin/pr/* > > > > then `git fetch` will retrieve all the pr as branches. Almost making it > > feel gerrit-like. > Oh that is nice.
Indeed! you can almost work exclusively without ever connecting to github, or the other way around! > > > Last but definitely not least: you can run automatic builds and > > > tests whenever you push a commit. > > > > And for user contributions, the pull requests from git could be synced > > > > as new branches on the merc repo on bitbucket (if that's what Bram > > > > chooses), in a way that is convenient enough for Bram to review and > > > > decide to merge or not. > > > +1 > > And this is what I mean when keeping both bitbucket and github in sync, > > all the PRs from github can be fetched automagically on the bitbucket > > repository, and integrated to the vim workflow. > Does that also include the issue/bug tracker? Will that also be > synchronized? Or do we have to disable the bug tracker in one location > and send the people to the other? That's what I tend to do when I got projects mirrored on several places. But it's really a matter of what will be the most comfortable process for committers, starting with Bram :-) > > Of course, it's a very rough idea, but there's been a few people really > > motivated to get vim's source on git/github, so you guys just do that? > While I also think, that would be the best solution (does anybody has > the skills to setup those 2 synchronized repositories?), it basically > comes down to what makes Bram most comfortable and how he can work the > best. afaict, people in the mozilla team work exclusively on git, whereas the main repository is mercurial. Though, they're 100% self-hosted. BTW, I believe that the MoFo could provide infrastructure shelter to a project such as Vim (even though I'm not part of it). > All the rest is just icing on the cake that will make other interested > people easier to get involved with, but that shouldn't be the main > reason for switching. indeed, and that's the whole point I'm trying to develop. Bram chooses, and then we can "ice" around that to make it comfy for everybody. HTH -- Guyzmo -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
