You could: Have a template repo with: those xxx.gitignore files in it: a .gitignore file with “xxx-gitignore-xxx” in it (in other word, with a content you can easily identify a .gitattribute filter driver (for each new repo, you clone it and can start with those files already there. Then you remove the remote ‘origin‘, or … Read more
From the docs for Git Ignore A leading slash matches the beginning of the pathname. For example, /*.c matches cat-file.c but not mozilla-sha1/sha1.c. Try changing vendor/ to /vendor/
Another GNU Make solution. You can do it using the define and export commands as follows: define GITIGNOREDS *.o depend endef SRCS = $(wildcard [a-z]*.c) EXES = $(SRCS:.c=) export GITIGNOREDS .gitignore: $(SRCS) echo $(EXES) | sed ‘s/ /\n/g’ > $@ echo “$$GITIGNOREDS” >> $@ You have to be careful of make expansions (i.e. $(x)) inside … Read more
wwwroot/app/**/*.js wwwroot/app/**/*.map The ** will match everything inside app, also multiple levels of subdirectories.
One of the reasons might be that you already committed that files to your repository. In that case adding them to .gitignore doesn’t prevent git from tracking these files. To fix that you should first remove them from repository like that: git rm -r target/ (If your project has modules, you need to include the … Read more
Your vendor directory is checked in to the repo. To remove it, go to your git repo root and run: git rm -r –cached vendor This will recursively (due to -r flag) remove vendor from your git repo. The –cached flag will keep the local copy of vendor directory in tact. Note that if there … Read more
The bug seems to be still present in the maven-archetype-plugin v3.0.1 . For those who do not want to downgrade the maven-resource-plugin. I managed to establish a more or less ugly workaround. First you rename the archetype-resources/.gitignore to __gitignore__ then inside the archetype-metadata.xml add <requiredProperties> <requiredProperty key=”gitignore”> <defaultValue>.gitignore</defaultValue> </requiredProperty> </requiredProperties> <fileSets> <fileSet> <directory></directory> <includes> <include>__gitignore__</include> … Read more
You should not need the **/: __pycache__/ *.pyc That should be enough. See for instance gitignore.io/python. Note the practice of adding a trailing / to ignore specifically a folder. Use git check-ignore -v — afile (that I mentioned in Sept. 2013, with Git 1.8.2+) to check which rule ignores a file. If the folder was … Read more
While being too specific, you can still version that file (meaning: not include it in the default .gitignore), as : it will be used only by pyenv it is a good addition to the README, in order to illustrate what version of python is recommended for the specific project, it can be overridden easily (if … Read more