Skip to content
This repository was archived by the owner on Feb 11, 2026. It is now read-only.

Best Practices: Github Projects

Ashley Kolodziej edited this page Jan 11, 2021 · 4 revisions

Use Projects to track progress towards launch

Github Projects are used for tracking the work status of tasks (prioritized, in progress, ready for review, and released). Different team members are responsible for different statuses:

  • Prioritized: Manually maintained by the creative director, with input from the team, during backlog grooming meetings.
  • In Progress: Automatically maintained by Github based on actions a designer or developer takes on issues. Designers and developers are responsible for consistently linking issues to pull requests in order for this to work. Cards move here when pull requests are opened.
  • Ready for Review: Automatically maintained by Github based on actions a designer or developer takes on issues. Designers and developers are responsible for consistently linking issues to pull requests in order for this to work. Cards move here when pull requests are closed.
  • Released: Manually maintained by the team member who is responsible for releases, typically the developer. When a new release is created and deployed, the developer will move all cards within Ready for Review to Released to signify the release is complete, and track which features have been released so far.

Clone this wiki locally