github-workflow

To set up a feature branch in the MAPL GitHub workflow, create your branch from the correct base branch, either `develop` or `release/MAPL-v3`, following the project's specific naming conventions to ensure proper version control and collaboration.

The MAPL version control workflow requires a specific commit message formatting standard to maintain code quality and consistency. Adhering to these commit conventions ensures clear tracking of changes and prevents accidental breaking changes during collaboration.

To submit a pull request for MAPL, you must complete the required prerequisites and fill out the designated PR template. Meeting these submission standards ensures your code changes align with project expectations and pass the code review process.

The MAPL branching strategy defines `develop` and `release/MAPL-v3` as critical base branches. It enforces strict branch management rules and feature branch naming conventions to prevent accidental breaking changes and maintain code quality across the version control workflow.

You should target `develop` for ongoing general feature work and `release/MAPL-v3` for changes specific to that version. Selecting the correct base branch is a critical rule in the MAPL Git workflow to prevent breaking changes and maintain project stability.