Merge requests

Well, since you are going to work within a team, it is absolutely mandatory to introduce you to merge requests.

The merge request is something you submit in order to inform your colleagues that your code is ready for merging, but needs to be reviewed first.

When you submit a merge request, you need to tick some points like:

• Did I remove unused code?
• Is my branch based on master?
• Have I updated the status on Jira?

You will find a checklist file named code_review_checklist in the boilerplates, containing all these criteria.

Once your merge request is ready, you ask for a code review.

Code reviews

A code review is the process of examining someone else’s code to ensure it meets certain standards before being merged into the main codebase.

It usually involves one or more developers to:

• Check correctness: does the code actually solve the problem it’s supposed to?
• Improve quality: is the code clean, readable, and maintainable?
• Ensure consistency: does it follow the team’s coding standards and best practices?
• Catch bugs early: are there logical errors, security issues, or performance concerns?
• Knowledge sharing: reviewing helps team members understand different parts of the codebase

If the reviewer approves, then the merge request can be merged into the main codebase, else the reviewer asks for some corrections or clarifications until they agree with the changes.

Finish line

You are now perfectly equipped with all our good standards and baselines to start a web application in the best conditions.

May you have some more questions, please feel free to ask to 'AUTHOR'.

We hope you have had a good time reading all of this, and we wish you a good luck with your project.