-
Notifications
You must be signed in to change notification settings - Fork 1
Repo Management Governance
John Moehrke edited this page Feb 8, 2023
·
4 revisions
See the New Repo Governance
Prior to a formal publication, the repository will often be open to all of the committee members for the domain owning the repository. This enables full participation. Some domains may choose to be more restricted.
Once a publication has been published (on profiles.ihe.net) then IHE needs to track all changes. Any requested changes should have a github Issue explaining the problem being resolved. Requested changes must be done by a pull-request that is approved by a co-chair of the domain.
Thus when a publication is published, the repository must be protected in the following way:
- the co-chair team is given Admin,
- the domain committee team is given Triage access.
- Require pull requests before merging,
- Require approvals --> 1
- Restrict who can dismiss pull request reviews --> The co-chairs of that repo domain
- Allow specific actors to bypass required pull requests --> The co-chairs of that repo domain
- Require conversations resolution before merging