-
Notifications
You must be signed in to change notification settings - Fork 28
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
publish features from PR branches to npm #311
Comments
michaelwittwer
added a commit
that referenced
this issue
Jun 10, 2020
michaelwittwer
added a commit
that referenced
this issue
Jun 10, 2020
configure #311-prerelease-deployment branch to be published on channel pr311
michaelwittwer
added a commit
that referenced
this issue
Jun 12, 2020
chore(build): move from travis to github workflows
🎉 This issue has been resolved in version 5.7.0-pr278.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 6.0.0-pr91.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 6.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
To be able to test new features easily we should provide a distributed package on npm for open Pull Requests, so we can gather early feedback on new functionality
Describe the solution you'd like
configure semantic-release to also release on branches whenever a PR is opened
The text was updated successfully, but these errors were encountered: