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

chore: remove unused nightly release from CI #719

Merged
merged 3 commits into from
Jul 19, 2024

Conversation

obulat
Copy link
Contributor

@obulat obulat commented Jul 15, 2024

πŸ”— Linked issue

Resolves #716

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

To keep the CI green when the necessary checks pass, and only have failing CI runs when there is an actual problem.

Copy link

netlify bot commented Jul 15, 2024

πŸ‘· Deploy request for nuxt-storybook pending review.

Visit the deploys page to approve it

Name Link
πŸ”¨ Latest commit a357e8a

@tobiasdiez
Copy link
Collaborator

I prefer to keep the nightly release (but add the secret to make it pass). Could you please readd it? Thanks!

@obulat
Copy link
Contributor Author

obulat commented Jul 16, 2024

I prefer to keep the nightly release (but add the secret to make it pass). Could you please readd it? Thanks!

Do you mean keep the nightly release, and delete the release.yml: a357e8a

@tobiasdiez
Copy link
Collaborator

Thanks again!

@tobiasdiez tobiasdiez merged commit 2ed72b2 into nuxt-modules:main Jul 19, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI actions do not publish packages to npm
2 participants