Update release.yaml #4330
Merged
Update release.yaml #4330
Conversation
This file contains 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
$GITHUB_REF is null so trying to use
`$ {{ github.event.release.tag_name }}`
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4330 +/- ##
=====================================
Coverage 99.7% 99.7%
=====================================
Files 357 357
Lines 39869 39869
=====================================
Hits 39749 39749
Misses 120 120 ☔ View full report in Codecov by Sentry. |
jeremyliweishih
approved these changes
Oct 6, 2023
christopherbunn
approved these changes
Oct 6, 2023
Merged
This was referenced Oct 16, 2023
Closed
Closed
Merged
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.
Pull Request Description
Closes #4331
$GITHUB_REF is empty so trying to use
$ {{ github.event.release.tag_name }}After creating the pull request: in order to pass the release_notes_updated check you will need to update the "Future Release" section of
docs/source/release_notes.rstto include this pull request by adding :pr:123.