You can stare at that code all afternoon but you won't spot the bug until a microsecond after you hit "commit".
this post was submitted on 16 Mar 2024
93 points (83.9% liked)
Programmer Humor
19572 readers
1995 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
I'm not sure I understand, what's wrong with this commit?
1 change, forgot to enable the setting previously
What am I looking at?
~~Whoever committed this change thinks updating the text on the UI for this system will automagically fix issue.~~
~~It’s like editing the HTML on your bank’s website to show you have $1B in the bank 😂~~
Issue here committer forgot to update UI to expose the feature person was working on
No, the settings already existed, they just forgot to expose it
That makes sense now. Thanks for extra context.
(Here's some more context: The button is in the UI, but it exposed a completely different function than advertised, probably due to being generated from copy-and-pasting the previous button)
Yeah without more context it just seemed they were renaming the setting as part of a larger diff
It says "1 changed file..." at the top
I'm not convinced that's it, but I don't know enough to explain why.