mad-i-t/Magento 2 actions

Test Build Deploy M2 projects

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Activelast commit Jun 30, 2026
License
MIT

Pinned Snippet

workflow.ymlSHA-pinned
uses: mad-i-t/magento-actions@296d730b03d3a9fee115fe046803b1f00bee8076 # v4.0

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
phpversion of php to use 7.1, 7.2, 7.3, 7.4, 8.1 or 8.2auto
processPossible values: build, static-test, integration-test, unit-test, phpcs-test, deploy-staging, deploy-production, cleanup-staging, cleanup-production, security-scan-[files|modules]build
themesspecify themes to build multiple values must be comma separated e.g (Magento/blank or Magento/blank,Magento/luma)
static_versioningspecify or not if static versioning should be enabled0
static_deploy_jobsjobs in setup:static-content:deploy -f -t Madit/default -t Magento/luma --jobs=8
langsspecify build languages multiple values must be comma separated e.g (fr_FR or fr_FR,nl_NL)
keep_releasesnumbers of builds / releases to keep after deployment (rotation). Possible values (int) e.g: 33
override_settingsoverride config and scripts dirs with your own setup/config, must respect default scalfolding 1 or 00
elasticsuiteyour src is using elasticsuite? 1 or 00
elasticsearchyour src is using elasticsearch? 1 or 0
opensearchyour src is using opensearch? 1 or 0
extensionphpcs check on a Magento module or code base. Possible values, Vendor, Vendor/MyModule or dir path using github repository scaffolding""
severityMEQP magento coding standard severity check1
standardMagento2, PSR2, PSR1, PSR12 etc... see magento-coding-standardMagento2
deployerdeployer-php custom configs. Possible values, no-permission-check (there will be no permission check of writable dirs)default
composer_versionforce composer version. Possible values 1 or 20
magento_versionthe magento version to install i.e 2.4.10
disable_modulesList of modules to be disabled during install, comma separated e.g: Magento_Sales,Magento_Config""
enableenables functionalities when installing magento possible values: pwa""
no_pushdo not push magento source code to github repo values 0|10
magento_onlyapply the process on magento code only (i.e magento dir)0
pwa_studio_onlyapply the process on pwa studio code only (i.e pwa-studio dir)0
testsuitecustom testsuite to be ran works for integration and unit testing e.g: "Memory Usage Tests"
integration_filterintegration test filter test in class e.g: testAppReinitializationNoMemoryLeak
integration_classpath to integration class path from dev/tests/integration e.g: "./testsuite/Magento/MemoryUsageTest.php"
unit_test_configUnit test custom config pathdev/tests/unit/phpunit.xml.dist
unit_test_subset_pathRun restricted unit test subset directory path
md_src_pathpath to source to be mess detected
rulesetRuleset path e.g ruleset path for mess detectordev/tests/static/testsuite/Magento/Test/Php/_files/phpmd/ruleset.xml
exec_pathpath to file or directory to exec, scan, etc... (phpstan).
node_versionnode version for pwa-studio and Hyvä theme builds15
versiongeneric version to be compounded with other variables e.g pwa-studio-install to specify pwa version
apply_patchesapply patches in m2-hotfixes dir or in .magento.env.yaml0

no outputs