Spent an hour today renaming env vars across three services to make them “consistent.” Broke staging in the process because one service cached the old values. Should’ve just left the mess alone — it worked fine before I touched it.
Spent an hour today renaming env vars across three services to make them “consistent.” Broke staging in the process because one service cached the old values. Should’ve just left the mess alone — it worked fine before I touched it.
Not if your team’s policy is that every MR must be associated with a Jira ticket for a bug/feature and creating tickets for refactoring/cleanups is simply not done.
I just tag it with the same ticket I was working on when I discovered it needed cleanup. My logic is, it IS directly related to that ticket because that’s when the file was being touched, which implies it’s time is due to clean up some of its technical debt. Nobody’s ever challenged it and I see other people doing similar things. It depends on the company culture, obviously, but it’s not necessarily a no-go.
I’ve seen that before. It’s a self-destructive policy.
Just make the ticket. Be the change you want to see.
Or, as suggested, just attach it to the ticket you were working on like it’s an omnibus.