do PM the 'git' way
The development process implied by Gitlab seems wrong.
- I don't ever want to do
git pullin my branch.
- I want the process of becoming a Purr Data developer to be nothing more than a) git clone and b) making a merge request
- I want to give permissions for people who want to help manage the issue tracker
- I want merge requests to trigger CI builds
For number 4 I suppose there needs to be some way of marking particular branches as CI triggers. I can't just let new users trigger CI for obvious reasons. But is there a way to manage that without going in to the CI machine and registering each and every runner to someone else's branch?