Jason NovingerM to [email protected] • 1 year agoThis is valid Python syntaxwww.bitecode.devexternal-linkmessage-square8fedilinkarrow-up13arrow-down10file-textcross-posted to: [email protected]python
arrow-up13arrow-down1external-linkThis is valid Python syntaxwww.bitecode.devJason NovingerM to [email protected] • 1 year agomessage-square8fedilinkfile-textcross-posted to: [email protected]python
minus-square@[email protected]linkfedilink2•1 year agoYeah, that’s true, auto formatters will always have cases which format weirdly and have a nicer alternative. But in the end, the formatting does not matter much, so we all benefit for it being formated one way, and one way only. How would you format on git server? Create commits automatically, or ammend commits on push?
minus-square@[email protected]linkfedilink1•1 year agoI… don’t actually remember. It was a server side hook, I guess it tackled a new commit at the end. But it has been too long ago. Nowadays I don’t enforce such strict formatting, I just comment on MRs where I notice transgressions. I never liked ammending commits. Had a colleague, team lead, who ammended other peoples commits. Ugh. That’s when I started signing my own work.
Yeah, that’s true, auto formatters will always have cases which format weirdly and have a nicer alternative.
But in the end, the formatting does not matter much, so we all benefit for it being formated one way, and one way only.
How would you format on git server? Create commits automatically, or ammend commits on push?
I… don’t actually remember. It was a server side hook, I guess it tackled a new commit at the end. But it has been too long ago.
Nowadays I don’t enforce such strict formatting, I just comment on MRs where I notice transgressions.
I never liked ammending commits. Had a colleague, team lead, who ammended other peoples commits. Ugh. That’s when I started signing my own work.