.gitignore only on local

For local ignores you should use the .git/info/exclude file, not .gitignore: Patterns which are specific to a particular repository but which do not need to be shared with other related repositories (e.g., auxiliary files that live inside the repository but are specific to one user’s workflow) should go into the $GIT_DIR/info/exclude file. The two files … Read more

Ignore all files with the same name in git

From git docs A leading “**” followed by a slash means match in all directories. For example, “**/foo” matches file or directory “foo” anywhere, the same as pattern “foo”. “**/foo/bar” matches file or directory “bar” anywhere that is directly under directory “foo”. For your case: **/[Tt]est* it also matches both upper and lower case.

Best Practice for Adding .gitignore to Repo

They should almost always be included, as their purpose is to ignore “output” files (compiled binaries, log files) which are going to be generated by anybody working with a clone of your project. They’re meant to be version-controlled and included with the repository. You should not use .gitignore files within the repository to ignore files … Read more

Telling git to ignore symlinks

This seems to be a better idea find . -type l | sed -e s’/^\.\///g’ >> .gitignore Find outputs a “./” prefix for all files. Unless you trim it off, gitignore is unable to act on them . Once you trim the “.\” at the beginning , it works like a charm

Hata!: SQLSTATE[HY000] [1045] Access denied for user 'divattrend_liink'@'localhost' (using password: YES)