Skip to content

Teamwork using GitHub Issues


Below is a playlist of a few videos explaining how we will use GitHub and Gitter in this class.

Basic Teamwork

  • Weekly meetings.
  • Weekly or bi-weekly Sprint Milestones.
  • End meeting by adding Issues for the next Sprint, assign them to people.
  • Start meeting by reviewing the finished Issues from the last milestone. Move old open issues to next Sprint, reassign if needed.

GitHub Issues Tips and Guidelines

  • Use @username to get that user’s attention, @josemvidal for me.
  • Use our milestones.
  • Create your own weekly or bi-weekly sprint milestones
  • Assign each issue to 1 person
  • Explain why you are closing the Issue. Adding “Closes #1” to your commit comment (anywhere) will do this for you automatically.
  • Child issues refer to parent using “for #1” or “child of #1”
  • Labels:
    bug something that needs to be fixed.
    enhancement new feature. A thing that needs to get done.
    duplicate this is issue is this same as another one. Link to the other one. Close this one.
    question answer it. Author closes it.
    client interactions. Give demo to client, get feedback from client, etc. #fbca04
    readme read it. Close it. Teachers will use this to provide feedback to you. #c2e0c6
    wontfix not gonna do it. Close it.
    Add your own!
  • If someone did not close an important Issue by the end of the sprint, un-assign them. Assign them to an issue that is not on the critical path. If it continues, fire them.