CI check is (I think, to be verified) not enforced for new (`v2.0`+) branches

[thbar]

GitHub has two ways to enforce things:

• branch protection rules (https://github.com/TransmodelEcosystem/NeTEx/settings/branches aka the old mode)
• rulesets (https://github.com/TransmodelEcosystem/NeTEx/settings/rules aka the new stuff)

While looking into #1035, I believe we have currently:

• the CI protection mechanism (CI must pass before a merge is possible) is active only for v1.3 (so: not useful), and uses the "old mode", see screenshot below
• a new ruleset is in place for new branches, but does not enforce (at least not currently) CI errors (e.g. you can merge despite a CI failure, if I read correctly)

Will investigate later, but as a first conclusion: I will move the "parent check" from the general protection ruleset, into a dedicated ruleset, to fix #1035.

Screenshots

Useful to fix this & document.

Classic branch protection rules (only targeting v1.3 at the moment)

Details

New ruleset (incorrect)

Does not include CI check, if I'm correct. And also, currently includes (cause of #1035) the "parent status check" for all branches

Details

[thbar]

I tried something (to be verified) here https://github.com/TransmodelEcosystem/NeTEx/settings/rules/16171342

run is not very descriptive, and comes from the fact that (afaik) there is no explicit name into this declaration:

NeTEx/.github/workflows/ci.yml

Lines 8 to 10 in 24040c1

	jobs:
	run:
	runs-on: ubuntu-latest

Heads-up @TuThoThai @skinkie @ue71603, in theory this should start enforcing CI check (tests) on recent (post v1.3) branches.

To be tested & verified though.