Hi! Here are a set of instructions for a standardized development environment, including recommended configurations, coding practices, and project guidelines. This document has been prepared to ensure consistency and efficiency throughout the software development process.
Here, we will discuss the commit patterns adopted in our project, following the guidelines of Conventional Commits. We will establish conventions for commit messages, making it easier to understand the changes made in the code.
In this section, we will present important recommendations for creating and reviewing Pull Requests (PRs). We will cover best practices to ensure that our PRs are clear, concise, and effective, facilitating the code review and integration process.
Here, we will highlight recommendations for conducting effective code reviews. We will explore best practices for providing constructive feedback, ensuring code quality, and promoting collaboration among team members.
In this section, we will describe the merge flow used in our project. We will cover the steps and recommended practices for integrating and reviewing changes in the source code through merges.
In this section, we will discuss the use of tags and versioning in our project. We will cover the principles of semantic versioning (SemVer) and recommended practices for assigning versions to software releases.
Here, we will outline language-specific coding standards used in our project. We will cover coding conventions, style, and language-specific best practices to ensure consistency and readability in the source code.