308
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 27 Feb 2026
308 points (98.4% liked)
Programmer Humor
30119 readers
394 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 2 years ago
MODERATORS
I have a project with a bunch of compose files that define the services I self host. I "deploy" the project by sshing into my server and doing "git pull" which means I'm often making changes that don't get tested before committing to source control. As a result I have long chains of commits like:
And now I'm wondering if I've been an llm this whole time
Let me introduce you to Ansible
Why not just edit the YAML directly on the server via a command-line text editor or SSHFS and then push from there when it works?
No the AI would have called it fixed, “production-ready,” committed, and pushed after the first refactor.
Make your changes in a new branch and rebase/squash when you push it to main.
This also means modifying your
git pullcommand to pull the correct branch. A small change perhaps, but may be harder than just committing to main lol.I had a similar problem with GitHub actions, it was hard to test without messing up the main repo history.