search

isaacs / github

Just a place to track issues and feature requests that I have for github
2.21k stars 129 forks source link

Add separate privilege to organization teams for issue management #268

Open ThiefMaster opened 10 years ago

ThiefMaster commented 10 years ago

Right now you need to give out full push access to let people assign tags etc. to issues. In case where only few people integrate code in the main repo this is not optimal since you might want to let contributors assign issues (to themselves) and set labels in the upstream repo but not give them full push access.

reedstrm commented 10 years ago

:+1: As we've grown, we've run into this. Especially wanting to allow QA staff who are not coders this access.

sharwell commented 10 years ago

This is a big deal. :+1:

patcon commented 9 years ago

+1

bhack commented 9 years ago

:+1:

bporterfield commented 8 years ago

+1

timabbott commented 8 years ago

:+1: -- just ran into this issue.

tsykora commented 8 years ago

+1

tveskrna commented 8 years ago

+1

JdeH commented 8 years ago

+1!

sypets commented 5 years ago

Please don't write +1 comments, use the thumbs up reaction instead.

CONTRIBUTING.md

smeijer commented 4 years ago

👍 As we've grown, we've run into this. Especially wanting to allow QA staff who are not coders this access.

2014... Feels like ancient history, and yet still so relevant in 2020.

We have a private repo with issue tracker. It would be awesome if we could add users to this repo that have permission to the issues, (and pull-requests?), but not to code.

So no pull-push rights, no clone rights, no access to the code tab. Basically, nothing that allows them to see or even copy our code. But everything to allows them to read and comment on issues, including the project boards.

This way we could easily add a third-party QA to a private repo, without worrying about our code. Freelancers on an hourly basis, whom you don't trust with your code. This would have so much potential.