Description: - Decide how the team will use issues, branches, commits, pull requests, and code reviews throughout the project. Tasks: - Define a branch naming convention. - Create relevant labels, such as setup, feature, ui, testing, documentation, and deployment. - Agree on a commit message format. - Decide how commits should be linked to issues. - Agree that all changes must go through a pull request and code review. - Acceptance Criteria: - The workflow is documented in the README or in a separate document. - All team members are familiar with the workflow. - At least one pull request has been tested and reviewed.