-
Notifications
You must be signed in to change notification settings - Fork 2
Collaborative workflow
Our team will use GitHub for code collaboration as well as general communication when possible, via three main channels:
-
GitHub Issues - We should use Issues for open discussion that is not connected to a proposed addition of / change to code.
-
Pull Requests - When a question/issue pertains to code, let's attempt to (if only partially) answer/resolve it through adding/changing code/tests/comments and submitting a GitHub Pull Request. Be sure to fork the repository and commit changes in a new branch (i.e. not master) before pushing your branch and submitting the pull request.
-
GitHub Wiki - The discussions attached to Issues and Pull Requests should serve as readable/searchable historical records of our decisions, especially after they are closed or merged, respectively. However, we should also use the Wiki to organize and summarize key decisions and information. We should also use the wiki to house records of "done" discussions (e.g. minutes from in-person meetings).