Skip to content
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

fix: fix deployment for storybook 7 #973

Merged
merged 1 commit into from
Jun 12, 2023

Conversation

clintonmedbery
Copy link
Contributor

@clintonmedbery clintonmedbery commented Jun 12, 2023

Closes D2IQ-97583

Description

This removes storybook deployer for using a more native action.

Which issue(s) does this PR relate to?

Testing

Not sure we can until it is merged.

Trade-offs

We no longer have a script to do this manually. Not sure we would want to anyways.

Checklist

  • This PR is associated with a JIRA and it is mentioned in the commit message footer ("Closes …")
  • Significant changes have been tested downstream to avoid breaking changes
  • This PR contains breaking changes and states in the commit message body ("BREAKING CHANGE: …")
  • I have reviewed the changes and provided detail to the sections above

@clintonmedbery clintonmedbery requested a review from a team as a code owner June 12, 2023 21:01
@github-actions
Copy link

github-actions bot commented Jun 12, 2023

Uffizzi Preview deployment-28315 was deleted.

Copy link
Collaborator

@nataliepina nataliepina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had a look at this during pairing. Thanks!

@nataliepina nataliepina merged commit 57ae60e into main Jun 12, 2023
@nataliepina nataliepina deleted the clintonmedbery/fix/gh-action-deploy branch June 12, 2023 21:23
@github-actions
Copy link

🎉 This PR is included in version 14.0.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@mstruebing
Copy link
Contributor

mstruebing commented Jun 13, 2023

With this change, we should make sure to update all branches with the latest main branch prior to merging as we do not execute tests anymore before publishing after a merge.

These are two separate actions now, so the tests could fail but we still publish. (We do not execute tests in any pre-npm lifecycle script).

Is anyone against me enabling that checkbox?

Screenshot 2023-06-13 at 12 09 38

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants