-
Notifications
You must be signed in to change notification settings - Fork 47
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
Migrate from Travis CI to GitHub Actions #646
Conversation
Do we really need to move since this is OSS? |
@@ -0,0 +1,73 @@ | |||
name: CI | |||
on: | |||
push: |
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.
are the trailing colons necessary 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.
Trailing colon is required, since it's a mapping, not a simple list/array. Docs explicitly say so
You must append a colon (:) to all events, including events without configuration
Yes. You'll see the ticket in the backlog shortly with more details, but this is mandatory. |
@grasmash The upstream action was approved, so this can be merged whenever you're comfortable with it. |
This is working and ready for review.
softprops/action-gh-release@v1
is approved and enabled on the org.Until this is merged, it won't actually run on the Acquia account. You can see test results for this feature branch on my fork: https://github.com/danepowell/cli/actions
You can also see a tagged release where Actions attached the phar: https://github.com/danepowell/cli/releases/tag/actions1