maint: add publish-dev step #113
Draft
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
https://circleci.com/developer/orbs/orb/circleci/orb-tools#jobs-publish If "dev" is selected, two tags will be created: dev:alpha and dev:SHA1
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.
DO NOT MERGE. Currently this is just publishing a dev orb from my branch to try things out.
Which problem is this PR solving?
Short description of the changes
according to orb-tools/publish docs on
pub_type:How to verify that this has the expected result
A merge to main should publish dev:alpha. Reviewing this I'm seeing other publishing happens in test-deploy so maybe this should live there? And/or we should move those steps back to the main file.
DO NOT MERGE. Currently this is just publishing a dev orb from my branch to try things out.