You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the title says, with deploy strategy link (e.g. hard links), upon issuing composer require package/x, sometimes no files or just some files are added to magento-root-dir/.gitignore.
Also, when issuing composer remove package/x, files are also not removed from the magento-root-dir either.
I tested this with various extensions and with my own extension, which only had 4 files. For my own extension, no files were added to .gitignore at all and in the case of the tested extensions from the firegento repo some files were missing from the .gitignore, most of the time files that are not in app/code/, e.g. files in skin/ or app/design/* etc.
Tested extensions were for example:
"aoepeople/aoe_scheduler": "^1.5" or
"connect20/ASchroder_SMTPPro": "^2.0"
Only changing the deploy strategy to something like symlink "fixes" this, e.g. .gitignore is populated as expected and files are deleted on composer remove as well.
The text was updated successfully, but these errors were encountered:
As the title says, with deploy strategy link (e.g. hard links), upon issuing composer require package/x, sometimes no files or just some files are added to magento-root-dir/.gitignore.
Also, when issuing composer remove package/x, files are also not removed from the magento-root-dir either.
I tested this with various extensions and with my own extension, which only had 4 files. For my own extension, no files were added to .gitignore at all and in the case of the tested extensions from the firegento repo some files were missing from the .gitignore, most of the time files that are not in app/code/, e.g. files in skin/ or app/design/* etc.
Tested extensions were for example:
Only changing the deploy strategy to something like symlink "fixes" this, e.g. .gitignore is populated as expected and files are deleted on composer remove as well.
The text was updated successfully, but these errors were encountered: