QE-12061 add publish gh actions #520
Merged
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
Test Results1 tests 1 ✅ 1s ⏱️ Results for commit 14bb127. |
chrome results288 tests 286 ✅ 16m 0s ⏱️ For more details on these failures, see this check. Results for commit 5651a9f. ♻️ This comment has been updated with latest results. |
unit results29 tests 29 ✅ 6s ⏱️ Results for commit 5651a9f. ♻️ This comment has been updated with latest results. |
ddl-cedricyoung
changed the title
ddl-bcolby
approved these changes
Aug 21, 2024
ddl-cedricyoung
changed the title
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.
PR Type
What kind of change does this PR introduce?
What is the current behavior?
We don't have an automated way to publish the package
Issue Number: https://dominodatalab.atlassian.net/browse/QE-12061
What is the new behavior?
add publish actions (test.pypi.org and pypi.org)
update project toml metadata
Does this PR introduce a breaking change?
Other information
Will have to test the new publish workflows post-merge