News for hackers. Stuff that matters.
Re:Go is moving to GitHub by jeffreyrogers on Thursday November 13, 2014 @08:04PM (#8605246)
It is great to see so many projects moving to git and GitHub in particular. GitHub is incredibly helpful for quickly taking a look at a project and figuring out what areas of a project are still evolving and being actively developed.
Re:Go is moving to GitHub by negated on Thursday November 13, 2014 @08:20PM (#8605292)
You could also say that everyone moving to GitHub is leading to a dangerous centralized monoculture that evaluates software quality based on how well it fits GitHub's conventions.
Re:Go is moving to GitHub by andrewchambers on Thursday November 13, 2014 @08:48PM (#8605402)
git is still git - people don't even need a github account to have full functionality.
Re:Go is moving to GitHub by icebraining on Thursday November 13, 2014 @08:58PM (#8605434)
How many Github projects accept git format-patch submissions? There's functionality beyond the basic DVCS commands.
Re:Go is moving to GitHub by dsymonds on Thursday November 13, 2014 @09:05PM (#8605459)
In Go's case, we will be using Gerrit (elsewhere) for accepting submissions. GitHub will only be used as a source code mirror, wiki and issue tracker.
Re:Go is moving to GitHub by NateDad on Friday November 14, 2014 @06:56AM (#8606704)
Wait wait wait... no pull requests? There's no way you could just hook up PR's to gerrit? Using github just as a mirror seems to defeat the entire purpose of github, which is to encourage more community members to contribute.
Re:Go is moving to GitHub by lmm on Friday November 14, 2014 @04:43AM (#8606419)
Having migrated projects from GitHub to/from Bitbucket and internal git servers - which is a 10 minute job at most - I'm not terribly worried about this.
Re:Go is moving to GitHub by yohanatan on Thursday November 13, 2014 @09:15PM (#8605493)
Re:Go is moving to GitHub by thejosh on Thursday November 13, 2014 @08:38PM (#8605366)
Moving to git is great, moving to github can be terrible for some projects that are more collaborative, as if you want to change someones PR you cannot..
Re:Go is moving to GitHub by reledi on Thursday November 13, 2014 @08:49PM (#8605406)
You can makes changes to a PR that you didn't open.

If you want to change the title, edit/delete comments, close the PR, assign a person or labels then you'll need the proper permissions.

If you want to make changes to the code you'll need to have push access to the same repo (which is usually the case if you're on the same team because then you don't need to use forks). Otherwise you can always amend the commit(s) before merging them into master.

Re:Go is moving to GitHub by andreabedini on Thursday November 13, 2014 @10:01PM (#8605613)
Better still you can fork the PR and open a PR to the PR :)
Re:Go is moving to GitHub by codygman on Friday November 14, 2014 @10:24AM (#8607517)
What if the repo is /me/myproject and you are trying to fork /contributor/myproject? What will your fork be named?
Re:Go is moving to GitHub by zwily on Thursday November 13, 2014 @08:50PM (#8605408)
They're using Gerrit for code review, where you can modify patches submitted by other people.