Hey all! My team at work is struggling with growing pains of getting into a formalized review process, so I was wondering if any of you guys have some things to live or die by in your code reviews. How much of it is manual, or how much is just static code analysis + style guide stuff, etc?

  • lackthought@lemmy.sdf.org
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    this is almost exactly how my company does it as well

    except merges are typically handled by specific people and they only reach out for reviews if they aren’t sure of how to handle a potential conflict