-
Notifications
You must be signed in to change notification settings - Fork 23
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
Enable-anyone-launch-release #3892
Conversation
🦋 Changeset detectedLatest commit: b7941bf The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
So I'm guessing the idea of this is that it doesn't actually auto-merge unless it passes CI yeah? But I suppose if it made its way to the changeset PR, it should have passed CI so it shouldn't ever fail. |
Co-authored-by: Cassandra <cassandra.tam@cultureamp.com>
@HeartSquared pretty much, this is what was recommended and used in FEF, so it's tested. |
Co-authored-by: Cassandra <cassandra.tam@cultureamp.com>
Why
When Changesets opens a PR it does not trigger GitHub actions, because its token does not have permission to. This is a hack to allow one of us to trigger GitHub actions for a changesets PR by enabling automerge on the PR.
What
Updated Github Action for ci to listen for
auto merge
trigger which will activate the ci checks