You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not quite sure if this is an appropriate venue for this, or if it should be a QEP or similar, but I'll start here.
For event pages (as the UC 2025 pages just merged) there are usually three things true - there'll usually be one or two people responsible for updating them from the LOC (local organizing committee), other potential reviewers likely won't be able to tell the validity of the information (as the PR might be the first time they see it) and there commonly is an urgency (especially the days before/during the event, where changes need to get out ASAP) that's not applicable for most other changes.
Therefore, I think it would make sense for an expedited PR process. Something along these lines:
LOCs can appoint 1-2 persons who get permission to merge PRs, including their own, touching only the specific event pages. PRs touching other parts require the usual review process.
I don't think that Github supports branch policies scoped to directories (not even with a CODEOWNERS file), so this would have to be a "soft" policy (i.e. the appointed persons get the ability to merge any PRs, but must promise to follow the process).
Reference to Feature
No response
The text was updated successfully, but these errors were encountered:
Feature Description
Not quite sure if this is an appropriate venue for this, or if it should be a QEP or similar, but I'll start here.
For event pages (as the UC 2025 pages just merged) there are usually three things true - there'll usually be one or two people responsible for updating them from the LOC (local organizing committee), other potential reviewers likely won't be able to tell the validity of the information (as the PR might be the first time they see it) and there commonly is an urgency (especially the days before/during the event, where changes need to get out ASAP) that's not applicable for most other changes.
Therefore, I think it would make sense for an expedited PR process. Something along these lines:
I don't think that Github supports branch policies scoped to directories (not even with a CODEOWNERS file), so this would have to be a "soft" policy (i.e. the appointed persons get the ability to merge any PRs, but must promise to follow the process).
Reference to Feature
No response
The text was updated successfully, but these errors were encountered: