Project: GitHub Workflow

For "Projects" in this Repository we currently have 4 swimlanes. These are subject to change.

Pull requests are not reflected in any swimlanes only issues. Pull requests if not related to any issue can be put in a lane.

• To Do: When issues are manually added to the project board or reopened they are automatically placed here
• Review/QA: When an issue is closed it will be automated as done and be moved here to be QA'd
• Done: Issues will be manually moved into this swimlane by QA or reopened which will move them back to "To Do" (Currently no automation for this column)

Note: When creating a Project board for a new release, copy an existing one to maintain the layout/automation (Menu->(...)->Copy on existing Project)

The current project board is https://github.com/tl-its-umich-edu/my-learning-analytics/projects/3

Dev Workflow

• Issues should be closed when they are merged and re-opened only if they fail QA.
• If you add a message in the first comment of a pull request like Closes #332 Fixes #332 it will close the issue when the PR is closed
• Issues should have a Milestone related to the next version
• Issues should have be put into a current project board

QA Workflow

• Look at the current project board.
  • Some issues need a developer to verify (or provide more information). Please use the label "dev review" to get developer attention
  • Move the card to the Done if it's verified
  • Move the card to the In Progress if it needs more work and this will re-open the issue.

Update

From a Slack conversation with @jennlove-um:

• the issue stays in progress until it is merged and closed, then it is automatically moved to the Review/QA column
• if it's something that requires developer testing, then it needs to be manually moved to the Review/QA - DEV column (that column was added and doesn't have any automation)

This is just a quick edit. It should be edited and moved to the workflow section(s) above.