Took 2 hours of reading through examples just to deploy the site.
Turns out, it is hard to do even just the bash stuff when you can't see the container.

you are viewing a single comment's thread
view the rest of the comments

[–] akash_rawal@lemmy.world 58 points 2 days ago* (last edited 2 days ago) (14 children)

Time for the yearly barrage of "Setup CI"..."Fix CI" commits.

That is my experience with basically every CI service out there.

[–] frezik@midwest.social 35 points 2 days ago (13 children)

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.

[–] Ajen@sh.itjust.works 5 points 2 days ago (2 children)

Line the other commenter said, there's nothing wrong with committing temp/untested code to a feature branch as long as you clean it up before the PR.

[–] frezik@midwest.social 3 points 2 days ago (1 children)

There are issues that come up in niche cases. If you're using git bisect to track down a bug, a non-working commit can throw that off.

[–] Ajen@sh.itjust.works 7 points 2 days ago* (last edited 2 days ago)

You might have misunderstood what I meant by "clean up before the PR." None of the temp commits should end up in the main branch, where people would be bisecting.

load more comments (10 replies)