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

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

32 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

[-] pattern@beehaw.org 2 points 1 year ago

This is super interesting, thank you for the info! Do you guys find a week for a merge too long?

[-] nigel_peters@lemmy.nz 2 points 1 year ago

Yeah it's probably one of our more hotly discussed issues at eng. catch-ups. A few newer starters come from more startup backgrounds and find it super frustrating.

Pros & cons as with any process 🤷

this post was submitted on 08 Jun 2023

20 points (100.0% liked)

Programming

13345 readers

1 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 1 year ago

MODERATORS

alyaza@beehaw.org

Hexorg@beehaw.org

remington@beehaw.org