20
What does your merge/code review process look like? (beehaw.org)
submitted 3 years ago by pattern@beehaw.org to c/programming@beehaw.org
33 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
[-] alehel@beehaw.org 1 points 3 years ago

Well. I told a slight lie. We go against develop. However, builds are created from develop. So we don't actually use main anymore. We used to, but our workflow changed over time untill we got to the point were we didn't use main anymore. I'm not even sure what we would use it for if we'd tried.

this post was submitted on 08 Jun 2023
20 points (100.0% liked)

Programming

15594 readers
42 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 3 years ago
MODERATORS
alyaza@beehaw.org
Hexorg@beehaw.org
remington@beehaw.org