Our current contribution process is for users to create a pull request to the main branch. A CUGOS member with write access to the repository must then approve that pull request before it is merged and incorporated onto the public website.
This workflow is already well documented and, I think, is well suited for contributions from external members or any design changes to the site that might break functionality. However, CUGOS members with write access may also want to make very minor contributions: for example, adding a new meeting or adding yourself to a meeting agenda.
Should CUGOS members with write access be able to bypass the PR approval requirement when making minor updates? It would be nice to have a standard practice for this situation that we include in the contribution guidelines.
Our current contribution process is for users to create a pull request to the main branch. A CUGOS member with write access to the repository must then approve that pull request before it is merged and incorporated onto the public website.
This workflow is already well documented and, I think, is well suited for contributions from external members or any design changes to the site that might break functionality. However, CUGOS members with write access may also want to make very minor contributions: for example, adding a new meeting or adding yourself to a meeting agenda.
Should CUGOS members with write access be able to bypass the PR approval requirement when making minor updates? It would be nice to have a standard practice for this situation that we include in the contribution guidelines.