Now is a good time to discuss workflows - what works for you and your team, what might work, and what you've been doing in the past. Here are some topics you will want to discuss with your team as you establish your ideal process. Have a conversation either synchronously or in issues in the class repository about different workflows.
- Which branching strategy will we use?
- Which branch will serve as our "main" or deployed code?
- How will you protect your code?
- Will we use naming conventions for our branches?
- How will we use labels and assignees?
- Will we use milestones?
- Will we have required elements of Issues or Pull Requests (e.g. shipping checklists)?
- Who is expected to review your work? Do you plan to involve other teams?
- How will we indicate sign-off on Pull Requests?
- Who will merge pull requests?
- How will you teach your workflow to your team? If it already exists, how is it taught to new hires?
- What integrations will be used in different stages of development? Will all teams be using the same tools?
- If users have questions about Git, GitHub, or their workflows, who do they ask? How do they know who to ask?