Setup branch protection for all resource repos

[SteveALee]

For each - take the branch listed in .gitmodules and

• apply branch protections:

  • Require a pull request before merging
  • Restrict who can push to matching branches

• check no one listed under collaborators and teams has > write access

• [x] wai-InvolveUsersAll

• [x] wai-InvolveUsersEval

• [x] wai-about-w3c-process

• [x] wai-about-wai

• [x] wai-accessibility-principles

• [x] wai-aria-practices

• [x] wai-arrm

• [x] wai-atag-report-tool

• [x] wai-audiences

• [x] wai-authoring-tools-list

• [x] wai-bcase

• [x] wai-cognitive

• [x] wai-combined-expertise

• [x] wai-components

• [x] wai-conformance-eval-overview

• [x] wai-contacting-orgs

• [x] wai-course-list

• [x] wai-curricula

• [x] wai-customize-design

• [x] wai-design-develop-overview

• [x] wai-develop-training

• [x] wai-easy-checks

• [x] wai-eval-overview

• [x] wai-eval-report-templates

• [x] wai-eval-standards

• [x] wai-eval-tools-overview

• [x] wai-evaluation-tools-list

• [x] wai-first-aid

• [x] wai-fundamentals-overview

• [x] wai-inclusion

• [x] wai-interactive-lists

• [x] wai-intro-accessibility

• [x] wai-intro-act

• [x] wai-intro-aria

• [x] wai-intro-atag

• [x] wai-intro-earl

• [x] wai-intro-linking

• [x] wai-intro-uaag

• [x] wai-intro-wcag

• [x] wai-media-guide

• [x] wai-mobile

• [x] wai-news

• [x] wai-older-users

• [x] wai-org-policies

• [x] wai-people-use-web

• [x] wai-people-use-web-videos

• [x] wai-personalization-standards

• [x] wai-perspective-videos

• [x] wai-plan-policies-overview

• [x] wai-planning-and-managing

• [x] wai-policies-prototype

• [x] wai-presentations2all

• [x] wai-pronunciation

• [x] wai-quick-start

• [x] wai-resource-list

• [x] wai-resource-template

• [x] wai-selecting-eval-tools

• [x] wai-shared-experiences

• [x] wai-sitemap

• [x] wai-statements

• [x] wai-std-gl-overview

• [x] wai-std-harmonization

• [x] wai-teach-advocate-overview

• [x] wai-tutorials

• [x] wai-video-standards-and-benefits

• [x] wai-wcag-em-overview

• [x] wai-wcag-em-report-tool

• [x] wai-wcag-mob-overlap

• [x] wai-wcag-supplemental

• [x] wai-wcag-understanding

• [x] wai-website

• [x] wai-website-data

• [ ] wai-website-deploy-test

• [x] wai-website-theme

• [x] wcag-act-rules

[SteveALee]

@shawna-slh are you aware of any I can leave out of above.

I intend to leave ACT, APG and Curricular until after meeting

[SteveALee]

@shawna-slh

I've added protection to all the above, even if have no non Team contributors or never will. Or if are not used in the wai-website repo.

I have NOT processed wai-aria-practices or wcag-act-rules yet as we might need to coordinate with the teams

A few observations:

• wai-inclusion - reduced access for some
• wai-accessibility - reduced access for some
• wai-policies-prototype - has bot with maintain access
• wai-=website - Shawn explicitly listed as collaborator but probably not needed

[SteveALee]

How to change to a new "published" branch in resource repos

1. Go to settings -> branches and find the current published branch
   • normally the one with the protection set - usually master
   • might need to check in wai-website .gitmodules files if more than one
2. Go to the code page and select that branch
3. click on the branch name, enter publication into the box and click the create branch:... link
4. Goto to the settings pages -> branches and select edit for the rule for the old published branch
5. Change the branch name to published and save
6. in the wai-website repo edit .gitmodules changing the branch name for resource repo to be published

Now resource editors just need to create a PR and assign to you as per the workflow instructions

[SteveALee]

All done and tested with wcag-act-rules, wai-intro-wcag and wai-aria-practices

[shawna-slh]

@SteveALee build error for change to wai-aria-practices

[SteveALee]

fixed - was over protection

[SteveALee]

All done and tested with wcag-act-rules, wai-intro-wcag and wai-aria-practices

[shawna-slh]

Hey @SteveALee Please wait to do more until after we talk. Thanks!

[SteveALee]

Sure, though I think the new protected branch has been added to all repos now.