Have you had code reviews? How were they organized?

Code review in my practice is organized as a mandatory step before merging changes into the main branch. Usually, the process looks like this:

• The developer creates a pull request (PR) with a description of the changes.
• One or more colleagues conduct a code review, checking quality, compliance with standards, architecture, and potential errors.
• Tools such as GitHub, GitLab, or Gerrit are used for commenting and discussion.
• During the review, comments are discussed, improvements are proposed, and sometimes tests are added.
• After all comments are addressed and the PR is approved, the changes are merged into the main branch.

This process helps improve code quality, share knowledge within the team, and reduce the number of bugs in production.