Assess and standardize branch strategy with respect to running Github Actions in Adoptium repositories

[smlambert]

This issue is to look at what branch strategy with respect to Github Actions in each of the active Github repositories in the Adoptium Github organization. It relates to a discussion topic brought up in Jan 18th community call (see minutes in this doc).

We can focus on the most active repositories under the Adoptium top-level project are as follows:

Temurin:

• https://github.com/adoptium/temurin-build
• https://github.com/adoptium/ci-jenkins-pipelines
• https://github.com/adoptium/jenkins-helper
• https://github.com/adoptium/mirror-scripts
• https://github.com/adoptium/github-release-scripts
• https://github.com/adoptium/installer
• https://github.com/adoptium/containers
• https://github.com/adoptium/infrastructure

AQAvit:

• https://github.com/adoptium/aqa-tests
• https://github.com/adoptium/TKG
• https://github.com/adoptium/aqa-test-tools

and then look at the less active repositories as to whether a strategy is required.

[ascheman]

I checked the Adoptium repositories for GH Action branch patterns (for push or PRs)

• I ignored jdkNN(u) repos as they are mirrored, right?
• From the remaining, about 25 contains GH actions
• Some use branch_ignore patterns
• Almost all use their respective default branch only (either main or master)
• Very few use additional branch names (e.g., production: cf. https://github.com/adoptium/api.adoptium.net/blob/main/.github/workflows/build-docker.yml)

Therefor we can conclude that there is no existing branching pattern in place which needs to be respected.