schnurrito@discuss.tchncs.de to Privacy@programming.dev · 1 month agoUK creating ‘murder prediction’ tool to identify people most likely to killwww.theguardian.comexternal-linkmessage-square12fedilinkarrow-up11arrow-down10cross-posted to: privacy@lemmy.mlprivacy@lemmy.dbzer0.comaboringdystopia@mander.xyznews@beehaw.orgunitedkingdom@feddit.uk
arrow-up11arrow-down1external-linkUK creating ‘murder prediction’ tool to identify people most likely to killwww.theguardian.comschnurrito@discuss.tchncs.de to Privacy@programming.dev · 1 month agomessage-square12fedilinkcross-posted to: privacy@lemmy.mlprivacy@lemmy.dbzer0.comaboringdystopia@mander.xyznews@beehaw.orgunitedkingdom@feddit.uk
minus-squareRonSijm@programming.devlinkfedilinkarrow-up0·1 month agoThat explains why that one junior developer that keeps force-pushing and keeps breaking my build server went into hiding
minus-squareheavydust@sh.itjust.workslinkfedilinkarrow-up0·1 month agoI had one like that too. We had to disable force-push on GitLab because our commits kept on disappearing.
minus-squareazron@lemmy.mllinkfedilinkarrow-up0·1 month agoForce push enabled in a team environment is asking for trouble.
minus-squareheavydust@sh.itjust.workslinkfedilinkarrow-up0·1 month ago“Force push with lease” in feature-branches that are controlled by 1 person only is fine though.
That explains why that one junior developer that keeps force-pushing and keeps breaking my build server went into hiding
I had one like that too. We had to disable force-push on GitLab because our commits kept on disappearing.
Force push enabled in a team environment is asking for trouble.
“Force push with lease” in feature-branches that are controlled by 1 person only is fine though.