-
Notifications
You must be signed in to change notification settings - Fork 308
feat: Validation and release on main push #2549
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
feat: Validation and release on main push #2549
Conversation
Co-authored-by: Mickey Ryan <[email protected]>
Co-authored-by: Mickey Ryan <[email protected]>
Co-authored-by: Mickey Ryan <[email protected]>
…main Co-authored-by: Mickey Ryan <[email protected]>
Co-authored-by: Mickey Ryan <[email protected]>
74fa0a7
to
0216c71
Compare
0216c71
to
99be0d1
Compare
824958b
to
7a7c2f7
Compare
7a7c2f7
to
6b9d076
Compare
bc1767b
to
1792779
Compare
Co-authored-by: Mickey Ryan <[email protected]>
Co-authored-by: Mickey Ryan <[email protected]>
Co-authored-by: Mickey Ryan <[email protected]>
821cfdc
to
fee517d
Compare
I think this is nearly ready to merge. We'll need to do some PR's into main to fully test the workflow. Currently, it can be tested by tweaking some of the triggers/if's. I think the only thing remaining to do is determine whether we're ok with the semver bump being dynamically determined by semantic commit messages (as noted above) |
093d604
to
a28ed39
Compare
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.
Reviewed in a campfire, everything looked good!
We noticed in the campfire that dataSourceIds
need to be a part of the schema and not the artifact. Mentioning this here for historical context.
- name: Build & Validate Artifact | ||
shell: bash | ||
id: build-validate-artifact | ||
run: | | ||
cd utils && yarn build-validate-quickstart-artifact | ||
cd utils && yarn build-validate-quickstart-artifact ${{ inputs.output-artifact && '--output-artifact' || '' }} |
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.
silly question, does this actually supply --output-artifact
? if inputs.output-artifact
is truthy?
in other words, would want a ternary here?
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.
Fun fact! You can't ternary in gh actions syntax :)
No description provided.