Try this: git status -s | grep -e “^\?\?” | cut -c 4- >> .gitignore Explanation: git status -s gives you a short version of the status, without headers. The grep takes only lines that start with ??, i.e. untracked files, the cut removes the ??, and the rest adds it to the .gitignore file.
Add this line to your .gitignore *_autosave* According to git help gitignore patterns match relative to the location of the .gitignore file Patternz like *_autosave* match files or directories containing “_autosave” somewhere in the name. Two consecutive asterisks (“**”) in patterns mathed against full pathname may have special meaning A leading “**” followed by a … Read more
Use this: git update-index –skip-worktree path/file.cfg And to restore: git update-index –no-skip-worktree path/file.cfg Lastly, if you want to list files that are marked with skip-worktree: git ls-files -v | grep ^S | awk ‘{print $2}’ To simplify, you can make an alias for that in your $HOME/.gitconfig: [alias] ls-ignored-changes = !git ls-files -v | grep … Read more
You should add it to gitignore file. Then, you should create requirements.txt file and populate it with the packages you have installed. Then, on your production server, create the virtual environment and run pip install -r requirements.txt. Read this to learn more about the requirements file.
The solution is to tell Git not to ignore sub directories: * !.gitattributes !.gitignore !readme.md !.gitkeep !*.php !*/ Otherwise, only the *.php files in the first directory level will be accepted and all sub directories will be ignored.
As illustrated here and detailed in “this question”, the function fnmatch() is involved to interpret glob patterns, which means regular expressions are not supported. This is what gitignore man page mentions: Otherwise, git treats the pattern as a shell glob suitable for consumption by fnmatch(3) with the FNM_PATHNAME flag: wildcards in the pattern will not … Read more
Take a look at the documentation of gitignore An optional prefix “!” which negates the pattern; any matching file excluded by a previous pattern will become included again. It is not possible to re-include a file if a parent directory of that file is excluded. Git doesn’t list excluded directories for performance reasons, so any … Read more
To ignore any file starting with ~$, use the pattern: ~$* Nothing more is needed.
It seems ! only works if the file is in the same folder. A possible workaround would be to nest the same statement till you get to your final file. A bit messy, but it works. public/typings/* !public/typings/browser public/typings/browser/* !public/typings/browser/ambient public/typings/browser/ambient/* !public/typings/browser/ambient/jquery public/typings/browser/ambient/jquery/* !public/typings/browser/ambient/jquery/jquery.d.ts
This is a common misunderstanding about the way .gitignore works we all met at some point when working with Git: .gitignore will ignore all files that are not being tracked yet; indeed, files that are already being tracked in your Git repository are not ignored by your .gitignore setup. To fulfil your need, it would … Read more