Reuse other workflows across repositories

[jpmckinney]

https://docs.github.com/en/actions/sharing-automations/reusing-workflows

• automerge (48)
• docker (12): 7 Django and 5 non-Django templates
• i18n (8): Django (cove-ocds, cove-oc4ids, pelican-frontend, data-registry), Babel
• js (6): only paths to files change
• lint (49): requires a few different versions or conditions, try using permissions: write at job level instead of PAT
• lint: profiles
• lint: extensions
• shell (7): only one exceptional case [+ profiles]
• spellcheck (7): different exceptions per repo [+ profiles]
• ci (6): for profiles only https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/evaluate-expressions-in-workflows-and-actions#example-matching-an-array-of-strings
• pypi: See Reuse PyPI workflows across repositories #121

Exceptions:

• cardinal-rs: lint.yml is too different (maybe adaptable to ocds-merge-rs once ready)
• data-registry: js.yml uses standard, since Biome doesn't yet support HTML Switch to Biome from standard data-registry#360

Too few to generalize:

• a11y: data-registry vs extension-explorer are quite different to build
• cove-ocds-live-tests: deploy
• deploy: extension-explorer vs bi.dream.gov.ua and bi.dream.gov.ua-mdcp are quite different to build
• release: cardinal-rs (maybe adaptable to ocds-merge-rs once ready)
• nonlinux: kingfisher-collect

Others:

• ci: too diverse (services, environment variables, app vs library, apt packages, ignore warnings, etc.)

Then:

• Update documentation and cookiecutters with respect to changed workflows
• Remove PAT secret if no longer used Needed in lint.yml to commit to protected branches

[jpmckinney]

To find workflows that don't reuse others:

Search steps: in *.yml,-ci.yml,-pypi.yml,-samples/*,-github/.github/*