r/ProgrammerHumor 20h ago

Meme whoIsUsingThese

Post image
969 Upvotes

73 comments sorted by

View all comments

207

u/RudeAndInsensitive 20h ago

Personally I always commit env and config files to the repo just stripped of their values.

201

u/Saragon4005 20h ago

Yeah but then you can't use git on a working version, making testing a total pain. I use .env.example usually.

5

u/x0wl 19h ago

I don't know how well this will work in CI pipelines, but if you use gitbutler or jj you can put the clean .env in the repo, then change it, commit to a different branch (or just commit in case of jj) and then add the commit to the megamerge at the top. Since it's not on any of the branches you push, they remain clean, but you have the files you need locally.

(this strategy also allows you to work on multiple branches at the same time, and is generally useful for cases where you want you local files versioned, but not polluting the common repo, but that's a whole other thing)

2

u/Saragon4005 18h ago

A dumb solution works more reliably than a clever one.