Project management 3. GitHub tools

Issues

Note: You can auto-close an issue with a commit message "fix #<issuenumber>" or "close #<issuenumber>"
Note: You can add todo lists into the description!
- Todo list can include links to other issues (just write #issuenumber)
- Don’t create a mega-issue “Sprint 1” or something like that, however
- We have a better tool for that…

A board that can be used to track sprint progress
GitHub has two Projects views
- Projects
  - Under one repo
- Projects (Beta)
  - Can have issues from multiple repos

Create a new project (not beta) for every sprint under Projects Tab > Projects (not beta!) > New Project
- Give name “Sprint 1”
- Use Project template “Automated kanban”
- Delete the default notes
Now, when an issue is closed, it jumps automatically to Done column

Kanban board has by default three columns of issues & notes
- To do
- In Progress
- Done
There can be issues, pull requests and notes in the columns
Notes can be converted into issues

The recommended way to merge a feature branch into the master branch
When a branch is ready to be merged into master, create a pull request in this tab
If the master branch maintainer doesn’t accept it right away, they can comment on the pull request page what needs to be changed before merge can be completed
If “All comments need to be resolved” is checked, the merge can only be completed after you’ve addressed the issues and the maintainer has approved the changes!
After making these changes, you don’t have to create a new pull request, new commits are automatically added to the one already created

You can search for issues or pull requests with specific dates, etc.
The syntax is versatile, check these links for more info:
- Searching issues and pull requests
- GitHub: Understanding the Search syntax