rudimusmaximus commented 6 years ago

because this repo is the public repo of a private user (not org), we need better access to the issues to collaborate on them. SO, we are using glo boards. With some risks. See #32 And also review how histories are updated with changes to issue summary line/title. Globoard users with edit access CAN EDIT EACHOTHERS comments.

[x] Set initiial protections for Develop and Master
[x] Review as group during sprints
[x] Document in a phase ii deliverable or update to existing repo
[ ] document rules around who can approve in review

rudimusmaximus commented 6 years ago

Currenlty set Develop and Master as shown here

RFJr. What do you think Rob?

RobGoelz commented 6 years ago

here's how we can handle code ownership, according to GitHub: https://blog.github.com/2017-07-06-introducing-code-owners/

rudimusmaximus commented 6 years ago

Changing Master branch rule to only require 1 approving review until or unless colead needs write access. Admin can override if need be.

RobGoelz commented 6 years ago

makes sense to me. thanks, Rudy!

rudimusmaximus / DevFlow

How to best set Branch Protection Settings for this project #31

Currenlty set Develop and Master as shown here