We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
v2.0
Taking down notes to document this (ping @ue71603, @TuThoThai, @ptitfred since this has been discussed with you), even if the fix is going to be easy.
The check I introduced in #1022 to avoid end-of-year costly backports is configured to run only for PR targeting either v2.1-wip or v3.0-wip.
v2.1-wip
v3.0-wip
NeTEx/.github/workflows/check-parent-branch.yml
Lines 9 to 11 in 24040c1
This is correct, but as seen in PR targeting branch v2.0 at the moment (e.g. #1030), the status check is verified, but doesn't actually run:
This is caused by the way the ruleset is configured.
I'll share & screenshot & modify it, which will unlock the situation while keeping the check on the correct targets.
Taking down notes to document this (ping @ue71603, @TuThoThai, @ptitfred since this has been discussed with you), even if the fix is going to be easy.
The check I introduced in #1022 to avoid end-of-year costly backports is configured to run only for PR targeting either
v2.1-wiporv3.0-wip.NeTEx/.github/workflows/check-parent-branch.yml
Lines 9 to 11 in 24040c1
This is correct, but as seen in PR targeting branch
v2.0at the moment (e.g. #1030), the status check is verified, but doesn't actually run:This is caused by the way the ruleset is configured.
I'll share & screenshot & modify it, which will unlock the situation while keeping the check on the correct targets.