Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run CI in release branches #5900

Merged
merged 1 commit into from
Oct 23, 2024
Merged

Conversation

eapolinario
Copy link
Contributor

Similar to flyteorg/flytekit#2827, this PR ensures that CI checks run as part of the merges to release branches.

Signed-off-by: Eduardo Apolinario <[email protected]>
@eapolinario eapolinario merged commit b5de6c1 into release-v1.13 Oct 23, 2024
16 of 43 checks passed
@eapolinario eapolinario deleted the run-CI-in-release-branches branch October 23, 2024 20:34
Copy link

codecov bot commented Oct 23, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (release-v1.13@ed2ce3b). Learn more about missing BASE report.

Additional details and impacted files
@@               Coverage Diff               @@
##             release-v1.13   #5900   +/-   ##
===============================================
  Coverage                 ?   6.91%           
===============================================
  Files                    ?     146           
  Lines                    ?   41729           
  Branches                 ?       0           
===============================================
  Hits                     ?    2886           
  Misses                   ?   38659           
  Partials                 ?     184           
Flag Coverage Δ
unittests-flyteidl 6.91% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant