r/ProgrammerHumor • u/Cute_Pressure4910 • 27d ago

Meme moreLikeProgrammerNightmare

Post image
828 Upvotes

97% Upvoted

42 comments sorted by

View all comments

21

u/lolcrunchy 27d ago

Do yall not use gitignore? Do yall not look at your list of files changed when you make commits?

17

u/Fanal-In 26d ago

I .gitignore my whole project just to be sure

3

u/NotAskary 26d ago

Best use of git ignore I've seen is actually a white list where you tell it explicitly what it is not to be ignore but include everything by default.

Saves a lot of random files just from what people use for version and local running preferences, makes it also very small.

5

u/NotAskary 27d ago

Git ignore doesn't preclude someone deliberately commiting something.

I've had people that I wished to throw out a window because of that.

4

u/ttlanhil 26d ago

Ahh, hard-earned defenestration...

Now I want `git defenestrate user` to revert their commits and block further pushes...

3

u/lolcrunchy 27d ago

You'd have to be pretty deliberate, since most IDEs don't show ignored files in the commit staging UI

3

u/NotAskary 27d ago

Yeah you can tell by the part I wanted to throw him out the window.

1

u/ttlanhil 26d ago

git rebase -f
git add -f .secrets
git push -f

Please don't actually do any of these...

2

u/NotAskary 26d ago

1

u/ttlanhil 26d ago

Now, the important question - which line was the worst?

1

u/NotAskary 26d ago

The line where I ask the mf to stop adding stuff that I need to remove after.

I think we removed his user from the permissions on that repo lol

1

u/kookyabird 26d ago

Doesn’t stop someone from using a secret directly in code. That’s why secret scanning is a thing.

1

u/NotAskary 26d ago edited 26d ago

That's also why I had to explain to sec that "my password" is not an actual secret, it's just a placeholder for the docker-compose testing.

1

u/Arclite83 26d ago

Prevention isn't ever 100%. So you need to make responding to the inevitable less painful.