Git uses the. gitignore setting to solve the problem that does not take effect or does not take effect. git. gitignore

Git uses the. gitignore setting to solve the problem that does not take effect or does not take effect. git. gitignore

The occasional problems are recorded as follows:

When we push a project, some configuration files or local files do not want to be uploaded to the server.

At this time, we will set the. gitignore File

It is generally set as follows:

###################*. Com *. txt *. class *. dll *. exe *. 7z *. gz *. iso *. jar *. rar *. tar *. zip *. log *. SQL *. sqlite *. pyc *. excude *. bakconfig. *. idea. DS_Store * ehthumbs.dbThumbs.dbconfig.pysetting.pytest.htmlbak.html untitled. idea

Have you noticed that config. * config. py is already defined?

The cause is that you want to screen all files starting with config.

However, the config. py file was uploaded as usual. At first, I thought it was a wildcard character error, but I wrote a direct file name.

Or not, change config. py to upload it.

It looks like the. gitignore setting does not take effect or does not take effect (you cannot drop the screen content)

Very troublesome.

I searched the internet and found more than one person who encountered this problem. I used this command to clear the cache and the. gitignore modification settings will take effect ..

Git rm-r -- cached.

The solution to the above git usage. gitignore setting does not take effect or does not take effect is to share all the content with you. I hope you can give us a reference and hope you can provide more support for the customer's house.