-
Notifications
You must be signed in to change notification settings - Fork 4
Developer Instructions
Sophie Lathouwers edited this page Jan 12, 2024
·
1 revision
There should always be a single person assigned to an issue who carries responsibility for the issue. Of course, more than 1 person can contribute to an issue.
Commits can only be added to the master
branch by means of a merge request. (Pushing to master
is disabled.)
The development flow ideally goes like this:
- Developer A is assigned to issue A.
- Developer A creates a branch for issue A by clicking the button in the issue.
- Developer A works in the created branch to address/solve the issue, and pushes the new commits to the repository.
- Developer A opens a pull request for their branch to be merged to
master
, and assigns developer B to it. - Developer B reviews the changes, and maybe requests changes in the merge request.
- When all issues with the merge requests are resolved, developer B merges it to
master
(by clicking the button).
When merge conflicts arise on a shared branch, we resolve them with git merge
. (Discussion)