After composer is installed, the plug-in is treated as GITsubmodule (GIT sub-project)

Using the YII2 framework, I am used to using composer to install the plug-in. after installation, I found that the Directory of the plug-in is treated as a GIT sub-project. the tool holder is submitted to the GIT of the project, but it is just an empty directory. There are several minor issues. 1. do you ignore vendor for git in online projects? In this way, collaboration is not feasible... using the YII2 framework, I am used to using composer to install the plug-in. after installation, I found that the Directory of the plug-in is treated as a GIT sub-project. the tool holder is submitted to the GIT of the project, but it is just an empty directory.

There are several minor issues;
1. do you ignore vendor for git of online projects? In this way, it is inconvenient for collaboration and deployment, mainly because composer is also difficult in China.
2. what should I do if I do not want to ignore the vendor folder and want to remove the recognition of this subitem?

Reply content:

Using the YII2 framework, I am used to using composer to install the plug-in. after installation, I found that the Directory of the plug-in is treated as a GIT sub-project. the tool holder is submitted to the GIT of the project, but it is just an empty directory.

There are several minor issues;
1. do you ignore vendor for git of online projects? In this way, it is inconvenient for collaboration and deployment, mainly because composer is also difficult in China.
2. what should I do if I do not want to ignore the vendor folder and want to remove the recognition of this subitem?

You must have selected a package.Dev-masterThe main reason is this.

1. In general, vender should be ignored. generally, it is about what to do during local development, and then composer update on the server at the time of release. It does not take vender as a file for release.
2. I don't know where the problem is. I didn't add it to git?

Modify. GitignoreVendor/Delete it.