I've collected all your responses and here's my new preliminary .gitignore_global:
# File Managers
# Backup files
# Temporary files
# Generated files
@fribbledom don't forget .swo
vim is weird
# DrRacket Backups
# Compiled racket bytecode
@fribbledom How about some stuff regarding key/password files?
I'm not sure how people usually upload their credentials, only that they do.
@fribbledom Additional temporary file patterns for Emacs:
@fribbledom A .gitignore should only cover artifacts caused bu the contained source code. Not those caused by the personal choice of editor and/or environment of a developer. https://twitter.com/coderbyheart/status/1212980450861420544
The reverse is also true: artifacts caused by the contained source code shouldn't be globally ignored. They'll be needed in certain cases. E.g. node_modules/package-lock are often tracked in SCM. Some CI will break: "but it works on my machine"
# Php composer
@fribbledom why are you ignoring the package-lock.json?
Arguably a wrong entry, yeah.
@fribbledom I guess you may want to if using yarn but if not usually you do want to check it in
@fribbledom There is always a step further. 😆
@fribbledom The corner of the Python world I'm in uses `dotenv` to stash secrets, so I'd add
# vim files
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!