this post was submitted on 13 Nov 2024
259 points (97.8% liked)
Programmer Humor
19564 readers
599 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Time for the yearly barrage of "Setup CI"..."Fix CI" commits.
That is my experience with basically every CI service out there.
Normally, you don't want to commit code unless it's been at least minimally tested, and preferably more than that.
All the CI's, however, force a workflow where you can only test it by committing the code and seeing if it works. I'm not sure how to fix that, but I see the problem.
If you can test it on a feature branch then at least you can squash or tidy the commits after you've got them working. If you can only test by committing to main though, curse whoever designed that.
Well, it does have triggers for other branches:
So, most probably would have a way to run it on other branches.
You can also use the
workflow_dispatch
execution pattern and use some data input params and execute through the portal interface.However, do be careful about trusting input params without sanitizing them (GH has docs around this).
Thanks, I'll look into that.
While trying this time (as you can see in one of the commits), I added
workflow_dispatch
at the wrong place, causing a problem. Later realised that it is part of theon