The same project A is developed by multiple people, but there is a config.php configuration file in project A. Different members have their own database environments. How to ensure that other members modify the local configuration file without submitting it, or submit it but Not overwriting the remote config.php?
Create a config.simple.php file, and then add the config.php file to gitignore, so that after different developers clone the code, they can change config.simple.php to config.php and replace it with their own configuration, like this It will not affect others just because someone changes the configuration
gitignore
gitignore file writing rules…
The topic can be summarized: In a distributed environment, how can files ignored by oneself not affect others
Using .gitignore files is not satisfactory, because .gitignore files will also be distributed to others along with the warehouse
It is best to control this file yourself
Then
you might as well try:
git config --global core.excludesfile $yourfilepath
.gitignore