|
|
|
|
|
by baleb
2577 days ago
|
|
I don't think that's true. If I understand you correctly, you mean files that are matched by rules in a .gitignore but staged using the -f option and then committed. The command this script uses to obtain the list of files to exclude is: git ls-files --directory --exclude-standard --ignored --others
A file staged and committed as described above is not listed using that command, and therefore not excluded from backups. |
|
Though it's not really just .gitignore anymore. Plus it depends on git and its performance... I'm just thinking of really large repos. This approach would basically mean that the tree is scanned twice.