Thank you for your interest in contributing to this project!
main: Contains the production code and is locked for direct commits.develop: Contains the code under development for the next release.feature/<name>: Used to develop new features.hotfix/<name>: Used to fix bugs.
To ensure the quality and stability of the production code, contributors should follow these steps:
- Create a new branch from
developfor their feature, - Once the work is complete, open a pull request
- Ensure that the pull request has a clear title
- The pull request must pass all tests and receive approval from reviewers
This workflow ensures that the main branch remains stable and production-ready.
-
Main Branches:
main: The primary branch containing the official release history.develop: The branch where the latest development changes accumulate.
-
Branch Types in our Workflow:
feature/<name>: For contributors to develop new features.hotfix/<name>: For contributors to fix critical bugs.release/<version>: Automatically created by GitHub Actions for preparing new production releases (not created directly by contributors).
-
Pull Request Process for Contributors:
- Each new feature should be developed in a
featurebranch. - A PR should be requested to merge the
featurebranch intodevelop.
- Each new feature should be developed in a
-
Release Creation:
- Once a new release needs to be created, a GitHub Action is manually triggered to create a release branch from the develop branch.
- A Pull Request is automatically issued to merge the release branch into the main branch.
- Final reviews and validations are performed at this stage.
- Merging the release branch into the main branch automatically creates a new release via another GitHub Action.