Programmer Humor

33517 readers

398 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
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.

founded 3 years ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

393

GitHub Actions radicalized me (lemmy.world)

submitted 1 year ago by carrylex@lemmy.world to c/programmer_humor@programming.dev

37 comments fedilink hide all child comments

Context: https://github.com/orgs/community/discussions/44490

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

[–] balsoft@lemmy.ml 2 points 1 year ago* (last edited 1 year ago) (1 children)

You write tests for functionality before you write the functionality.

You code the functionality so the tests pass.

Then, and only then, the test becomes a regression test and is enabled in your CI automation.

If the test ever breaks again the merge is blocked.

I disagree. Merging should be blocked on any failing test. No commit should be merged to master with a failing test. If you want to write tests first, then do that on a feature branch, but squash the commits properly before merging. Or add them as disabled first and enable after the feature is implemented. The enabled tests must always pass on every commit on master.

[–] wewbull@feddit.uk -1 points 1 year ago (1 children)

So I can never commit a test without also implementing the functionality?

That's madness.

[–] balsoft@lemmy.ml 2 points 1 year ago

You can, but not on master.