We have some control over the repo, but, as it isn’t in our org there are some limitations.
I would like to create a group of users that can can be assigned issues, but not push. We have support questions and such that would benefit from assignment in this way, while still retaining a pull request workflow. Wiki edits would also be possible by such a class of user.
In addition to [project] administrators a group [project] collaborators with Read Access would be useful to us.
Thoughts?
I was thinking of creating a mirror of the mirror to have greater control of groups and membership, but all kalatheme issues would be lost that way… Might that be a good strategy moving forward for new projects?
at https://github.com/drupalprojects/kalatheme
We have some control over the repo, but, as it isn’t in our org there are some limitations.
I would like to create a group of users that can can be assigned issues, but not push. We have support questions and such that would benefit from assignment in this way, while still retaining a pull request workflow. Wiki edits would also be possible by such a class of user.
In addition to [project] administrators a group [project] collaborators with Read Access would be useful to us.
Thoughts?
I was thinking of creating a mirror of the mirror to have greater control of groups and membership, but all kalatheme issues would be lost that way… Might that be a good strategy moving forward for new projects?