News for hackers. Stuff that matters.
Re:Ask HN: What tone to use in code review suggestions? by physicsguy on Monday June 27, 2022 @04:54PM (#31900653)
Tools are easy. You add it to the CI/CD pipeline, it fails if it doesn’t meet the guideline, people have to run the tool to get the merge in. On first run it’s painful, so if you’re not starting a project, use an autoformatter so it’s not all manual work. If you really want, you can even make your CI pipeline push commits with autofixes

Of course if you don’t have a CI pipeline that’s easy to integrate steps like this, you’ve got major issues to deal with elsewhere…

Re:Ask HN: What tone to use in code review suggestions? by thewebcount on Thursday June 30, 2022 @07:44PM (#31940213)
I don't have the permissions to add it to the CI/CD pipeline. I've filed bugs on our CI/CD to add it, but it's apparently not a high priority (you know, until someone sits down to review code, then suddenly it's the most important thing in the world).
Re:Ask HN: What tone to use in code review suggestions? by physicsguy on Monday July 04, 2022 @04:07AM (#31974662)
If I were you, I’d be looking to move on from your company then. Developers should own the testing part of the pipeline at the very least.