What does your merge/code review process look like? (beehaw.org)

submitted 1 year ago by pattern@beehaw.org to c/programming@beehaw.org

4 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[-] jmcs@discuss.tchncs.de 1 points 1 year ago* (last edited 1 year ago)

At my work we use trunk based development, with mandatory review before merging (enforced by tooling). Part of the review is ensuring proper test coverage and it's enhanced by static code analysis.

this post was submitted on 08 Jun 2023

0 points (NaN% liked)

Programming

10 readers

105 users here now

All things programming and coding related. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

admin@beehaw.org

alyaza@beehaw.org

Hexorg@beehaw.org