Git Group Workflow
<p>I often get confused when working with git when more than one person is involved. Using it for my own projects I never use the advanced features and only push to GitHub to share publicly. I am unsure of how to resolve issues working in a community.</p>

<ul>
<li>I join a project and create my own fork on github</li>
<li>I select an issue to resolve and create a branch "Issue #94"</li>
<li>I code and commit until I am happy</li>
<li><p>Create a final commit, comment on what was solved, use Github refernce tags to reference the issue (Fixes #94, Closes #94, etc)</p></li>
<li><p>Rebase and squash my branch to keep the project clean</p></li>
<li>Issue a pull request with the project leader</li>
</ul>

<p>This is where I get unsure of things. A pull request can take a few days to be merged. If I want to keep developing where do I go? </p>

<p>Should I back out of my branch and open a new branch for a new issue?</p>

<p>What if I am working on an issue and there are important updates to the master branch? Do I pull the new master and diff my changes to a new branch from that new master?</p>

<p>Once my pull request is accepted I can pull the new master and abandon my local branch but synchronizing all that across two repos gets confusing.</p>

<p>What is the commonly accepted workflow and is there a writeup I can pin to my cheatsheet?</p>