Post publish workflow to update main after the 1.3.0 release #587
Conversation
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
* Don't commit version changes if empty * Add conditional for pushing commit to branch * Use GITHUB_OUTPUT for check * Move brackets outside whole expression * Add a fi statement. Use a boolean variable
dixonjoel
requested review from
csjall,
pbirkhol-ni,
bkeryan and
nstokes-nati
as code owners
dixonjoel
force-pushed
the
users/jdixon/post-publish-workflow
branch
from
845b9d3 to
7b01f37
Compare
bkeryan
approved these changes
Jan 12, 2024
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.
What does this Pull Request accomplish?
Update publish_nims.yml with the changes made in releases/1.3.0. Update examples to use the newly released 1.3.0 packages. Update readmes to account for the new version of MeasurementLink.
Why should this Pull Request be merged?
Update main for the new 1.3.0 release.
What testing has been done?
None.