xia@lemmy.sdf.org to Programmer Humor@programming.devEnglish · 2 days agoThey can see the policy working...lemmy.sdf.orgexternal-linkmessage-square32fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1external-linkThey can see the policy working...lemmy.sdf.orgxia@lemmy.sdf.org to Programmer Humor@programming.devEnglish · 2 days agomessage-square32fedilink
minus-squaremmddmm@lemm.eelinkfedilinkarrow-up0·2 days agoHum… Ignore linter advice for code that you temporarily mangled. It’s not like you have to act upon it as soon as a blue line appears under your code.
minus-squarebleistift2@sopuli.xyzlinkfedilinkEnglisharrow-up0·2 days agoDepending on the configuration, a linter may cause the compilation or a CI pipeline to fail.
minus-squaremmddmm@lemm.eelinkfedilinkarrow-up0·2 days agoFailing your local compilation due to linter problems is just stupid. Sending “temporary” changes into your CI pipeline isn’t even stupid, it’s borderline malicious.
Hum… Ignore linter advice for code that you temporarily mangled.
It’s not like you have to act upon it as soon as a blue line appears under your code.
Depending on the configuration, a linter may cause the compilation or a CI pipeline to fail.
Failing your local compilation due to linter problems is just stupid.
Sending “temporary” changes into your CI pipeline isn’t even stupid, it’s borderline malicious.