Skip to content

Magento2: keep shared deployment configuration trackable - #4933

Open
Shubham-Padkonde wants to merge 1 commit into
github:mainfrom
Shubham-Padkonde:fix/magento-shared-configuration
Open

Shubham-Padkonde wants to merge 1 commit into
github:mainfrom
Shubham-Padkonde:fix/magento-shared-configuration

Conversation

@Shubham-Padkonde

Copy link
Copy Markdown

Link to the application or project's homepage

Magento Open Source

Reasons for making this change

The Magento 2 template ignores app/etc/config.php, hiding the shared deployment configuration (including enabled modules) from a project's initial commit. Adobe's deployment workflow explicitly requires this file to be versioned and shared across development, staging and production.

Remove that ignore rule and explain the distinction beside app/etc/env.php, which remains ignored because it contains environment-specific and sensitive settings. This only changes the Magento 2 community template.

Validation with a fresh Git repository and git check-ignore --quiet --no-index: before the change, the shared configuration is incorrectly ignored; afterward, all 17 path checks pass. These include env.php, generated code, vendor files, cache/static/media output, the existing .htaccess exceptions, application source and Composer manifests. git diff --check passes.

AI assistance was used to investigate and validate this change.

Links to documentation supporting these rule changes

Merge and Approval Steps

@Shubham-Padkonde
Shubham-Padkonde requested a review from a team as a code owner October 24, 2026 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant