Skip to content

add vendor directory to .gitignore #414

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

Closed
wants to merge 1 commit into from
Closed

add vendor directory to .gitignore #414

wants to merge 1 commit into from

Conversation

Flyingmana
Copy link
Member

never ever put your vendor directory into your vcs

# never ever put your vendor directory into your vcs
@maksek
Copy link
Contributor

maksek commented Nov 20, 2013

@Flyingmana why do i need to put the directory in gitignore? if i don't use folder name "vendor"? :)

@Flyingmana
Copy link
Member Author

because magento starts to use composer and in future sure will use it to install libraries and so on.

composer puts all this libraries and so on inside the vendor directory. So if you use Composer, you will need to ignore the directory composer uses.

(thats configurable, vendor is only the default used one)

Is this enough as an answer?

@maksek
Copy link
Contributor

maksek commented Nov 20, 2013

@Flyingmana, it is enough as an answer, does it make more sense to add it into .gitignore after officially Composer will be introduced within magento packages?

@Flyingmana
Copy link
Member Author

we have already an composer.json so now is a good time for adding also the vendor directory to .gitignore

@SchumacherFM
Copy link
Member

This Magento2 composer.json should not be treated as the root project and therefore you have to avoid putting vendor into this .gitignore.

Create your own root composer.json/repository and add there vendor to your gitignore and make Magento2 as a required module. That setup makes it also easy to update Magento2 to different versions.

@Flyingmana
Copy link
Member Author

I see, but commonly the unit-tests should work outside the context of a project.
So as long as there are unit-tests which should run standalone inside this project, you will need to load the required libraries (currently zero, but they will increase with rework the /lib directory)
So in the end, you will still have situations, where you need to ignore vendor.

@verklov
Copy link
Contributor

verklov commented Jan 21, 2014

@Flyingmana , thank you for reporting this issue! We are considering using Composer in Magento 2. Please watch the most fresh code we are deploying each Friday to the GitHub for updates.

@verklov
Copy link
Contributor

verklov commented Sep 10, 2014

The team processed this pull request and added vendor directory to .gitignore. We are closing this ticket now. Thanks again for your contribution!

@verklov verklov closed this Sep 10, 2014
magento-team pushed a commit that referenced this pull request Mar 11, 2016
magento-engcom-team added a commit that referenced this pull request Mar 6, 2019
 - Merge Pull Request magento/graphql-ce#414 from magento/graphql-ce:extended-customizable-options
 - Merged commits:
   1. 026e68f
   2. 03afb46
   3. 8df5cab
   4. 2167424
   5. cbc40cf
   6. 73d1c96
magento-devops-reposync-svc pushed a commit that referenced this pull request May 24, 2022
…dmin-ui-plugins

CABPI-227: Refactor admin UI plugins
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.

4 participants