-
Notifications
You must be signed in to change notification settings - Fork 26
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
Create a separate CI workflow for branch-YY.MM & main branches #466
Create a separate CI workflow for branch-YY.MM & main branches #466
Conversation
…ey aren't defined on push events
…ey aren't defined on push events
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets make a spreadsheet of the CI steps and what should run in each scenario and revisit this PR
…ci-branch-workflows [no ci]
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## branch-24.06 #466 +/- ##
================================================
- Coverage 74.08% 74.06% -0.03%
================================================
Files 403 403
Lines 14401 14401
Branches 1132 1132
================================================
- Hits 10669 10666 -3
- Misses 3732 3735 +3
Flags with carried forward coverage won't be shown. Click here to find out more. see 4 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Description
Prevents an issue where creating a release PR triggers two CI jobs:
pull-request/NNN
branch created by the PRbranch-YY.MM
Unfortunately the changes for
branch-YY.MM
andmain
can't be tested until after the changes are merged.Closes #459
Checklist