xia@lemmy.sdf.org to Programmer Humor@programming.devEnglish · 1 year agoThey can see the policy working...lemmy.sdf.orgimagemessage-square33linkfedilinkarrow-up11arrow-down10
arrow-up11arrow-down1imageThey can see the policy working...lemmy.sdf.orgxia@lemmy.sdf.org to Programmer Humor@programming.devEnglish · 1 year agomessage-square33linkfedilink
minus-squaremmddmm@lemm.eelinkfedilinkarrow-up0·1 year 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·1 year agoDepending on the configuration, a linter may cause the compilation or a CI pipeline to fail.
minus-squaremmddmm@lemm.eelinkfedilinkarrow-up0·1 year 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.