News for hackers. Stuff that matters.
Re:Protected branches and required status checks by asb on Thursday September 03, 2015 @01:38PM (#10166350)
Github still offer pretty weak configuration of permissions. e.g. the Dolphin team decided against migrating to Github due to the poor flexibility in permissions. https://dolphin-emu.org/blog/2015/09/01/dolphin-progress-rep... You can't have users who have the ability to triage issues without also giving them write access to the repository. https://help.github.com/articles/permission-levels-for-an-or...
Re:Protected branches and required status checks by chralieboy on Thursday September 03, 2015 @04:50PM (#10167452)
We struggle with that last one all the time. Our sales team can't add issues with tags or assign them without write access to the repo. So they just have to dump them in issues and then engineers have to categorize them.
Re:Protected branches and required status checks by sytse on Tuesday September 08, 2015 @01:51PM (#10187203)
In GitLab there is a more granular permission model, reporters can edit the labels but not see the code, see https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/perm...