ci: auto-enable very_long_running tests on release branch pushes#567
Merged
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
olivermeyer
requested review from
a team and
helmut-hoffer-von-ankershoffen
as code owners
|
kruegener
approved these changes
Apr 24, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
Release branches must be fully validated before publishing. The
very_long_runningtest suite was never included automatically, meaning some test cases weren't part of the build reported to Ketryx.How?
Added a third OR-condition to the
e2e_very_long_runningstep'sif:expression in_test.yml:(github.event_name == 'push' && startsWith(github.ref, 'refs/heads/release/v')). In a reusable workflow, these context variables reflect the caller's trigger, so this fires on direct pushes to release branches but not on PRs targeting them (whereevent_nameispull_request). Updated.github/CLAUDE.mdto document the new behaviour.