-
Notifications
You must be signed in to change notification settings - Fork 117
Create CI for testing project creation #75
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
Conversation
c69b2c8 to
bf33e57
Compare
Co-authored-by: Divesh Pahuja <divesh.pahuja@pimcore.com>
Co-authored-by: Divesh Pahuja <divesh.pahuja@pimcore.com>
|
Thanks for taking a look at my PR. I addressed your feedback. The PR might be somewhat stale now. If there is interest I can get it up to date. |
@yariksheptykin yes, we would like to merge 😉 so please update it. thanks! |
|
@yariksheptykin just that you know. we pushed some changes to the PR and now the action is running. |
|
@yariksheptykin New builds will be better with install checks 🚀 thanks a lot!! |
|
@yariksheptykin I have created an issue for demo as well pimcore/demo#302. if you like you can provide a PR. thanks! |
This MR adds CI pipeline for smoke-testing this skeleton on PRs and pushed to 10.x branch.
I am not familiar with Github Actions so I tested this CI first on my fork: https://github.com/yariksheptykin/skeleton/actions
To me it seems to do what I want it to do. What I am not sure about is that CI triggers are configured properly. The intentions is to run it on all PRs against 10.x branch and on pushed to 10.x branch. To my surprize this PR does no seem to trigger the CI, which I expected.