Follow

I've collected all your responses and here's my new preliminary .gitignore_global:

# File Managers
.directory
.Trash*
.DS_Store
.Spotlight-V100
.nfs*
._*
Thumbs.db
[Dd]esktop.ini
*.lnk

# Backup files
*~
*.bak

# Temporary files
*.swp

# Logs
*.log

# Databases
*.db
*.sqlite
*.sqlite3

# Binaries
*.a
*.o
*.so
*.dylib
*.exe
*.dll

# Generated files
**/build
**/.cache

## Java
*.class

## Python
*.py[oc]
**/__pycache__

## Javascript
**/node_modules
package-lock.json

@fribbledom
# DrRacket Backups
*.rkt~
\#*.rkt#
\#*.rkt#*#

# Compiled racket bytecode
**/compiled
*.zo
*.dep

@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. twitter.com/coderbyheart/statu

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"

@fribbledom Hmm, I would recommend taking out the rules for Javascript. You’ll usually want to exclude node_modules, but it’s important that that exclusion applies for everyone, and not just your local environment. (Also package-lock.json should almost always be committed in the repo.)

@fribbledom I guess you may want to if using yarn but if not usually you do want to check it in

@fribbledom Nit: package-lock should usually be committed, especially for applications. The advice from the npm folk is to commit it regardless. docs.npmjs.com/files/package-l

@kyli @fribbledom It is so tragic that this repo has a gitignore for everyone else, but not one for itself.

@fribbledom The corner of the Python world I'm in uses `dotenv` to stash secrets, so I'd add

.env

Sign in to participate in the conversation
Mastodon

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!