Form a System for Git Branching

garylli commented 3 years ago

Description

Now that we've done away with the idea of having concrete pairs, we might want to rediscuss how we're going to approach branching during development, testing, and pipeline modifications.

Checklist

[x] Discuss possible ways of branching
[x] Form a concrete branching standard
[x] Write ADR

garylli commented 3 years ago

Update 2/10/2020

For code development: We decided to continue branching by pair per task (if you have a partner) to encourage partner programming and reliability. If a person doesn't have a partner, they'll just create their own branch per task (jackson-css) etc.

For any other content modification: We decided to simply commit to master branch. We decided that any group work does not need its own branch and does not need review and can be directly added to master.

Finished:

Discussing branching
Concrete standard.

garylli commented 3 years ago

Update 2/15/2020

Link to ADR

Finished:

Creating ADR for branching

closes #37

19lmyers / cse110-w21-group14