-
Notifications
You must be signed in to change notification settings - Fork 12
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
feat: run setup:di:compile on push #116
base: main
Are you sure you want to change the base?
Conversation
This also needs a workflow that tests the behavior against the stable branch of the MageOS repo. |
@@ -0,0 +1,60 @@ | |||
name: "Magento compilation (setup:di:compile)" |
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.
We need a test of this action here: https://github.com/mage-os/github-actions/blob/main/.github/workflows/_internal-setup-di-compile.yaml
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.
@damienwebdev @Tjitse-E the target of this link doesn't exist anymore, what should we do here?
@Tjitse-E @damienwebdev can we merge this also if we don't have the workflow inside this PR? The workflow is here: mage-os/mageos-magento2#33 |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the new behavior?
Run
php bin/magento setup:di:compile
on pushes, only when files are pushed that can actually break compilation in Mage-OS (PHP, XML or composer changes).Example fail.
Does this PR introduce a breaking change?