Chapter 6 GitHub + ZenHub

TeamPSD’s main platform for project tracking is GitHub + the extension of ZenHub for project management.

6.1 GitHub Repositories

6.1.1 Workflow

6.1.2 Non-VA Repositories

  1. lzim/teampsd (Public) This repository contains TeamPSD resources and track the work that the team uses internally (i.e. Bookdown, document_team, depend_products, etc.)
  2. lzim/mtl (Public) This repository supports Modeling to Learn and contain the content in describe_learners, detail facilitators, and SIM/Model Code.
  3. lzim/sim (Public) This repository supports the Modeling to Learn Simulation User Interface plaform, Forio Epicenter, & and model files from Vensim DSS.
  4. lzim/research (Private) This repository holds the analysis for the (R01, IIR, R21) and disseminate science.
  5. lzim/mtl_team_tracker (Private) This repository is used by VA Clinicians and Modeling to Learn Co-facilitators to track team progression.

6.1.3 VA Enterprise Repositories

  1. “va/mtl” (operations pipeline) This repository stores the operations code used to support Modeling to Learn teams.
  2. “va/research” research pipeline) This repository holds the backend code that needs to stay internal for our grants.

6.2 Manage with ZenHub

Team PSD uses the GitHub Google Chrome extension, ZenHub, for agile project management.

We use ZenHub to: - see all of our Team PSD’s workflow at a glance. - organize and prioritize existing issues and features. - track dependencies across workgroups. - plan for our month’s work in a Epic and plan for further Epics down the road.

6.2.1 Enable ZenHub within GitHub

Click here for the ZenHub Google Chrome extension.

6.2.2 View Roadmap + Epics

6.2.3 Add Epics to Issues

6.2.4 Define Workspaces

6.2.5 Add Dependencies

6.2.6 Estimate Issues

6.2.7 9 Clicks for Issues

6.2.8 Manage Workgroup Workflows

6.2.9 Filter Workspace

6.2.10 Track Notifications

6.2.11 Create & Manage Issues

6.2.12 View Reports

6.2.13 Test First Epic (go_live)

6.3 Track Issues & Features

6.3.1 Create Issue/Feature cards [click maps in progress]

Click map would explain process here

6.3.2 Maintaining Cards [flow map in progress]

Flow map to maintain your issue/features cards as they get worked on.

We will wait for these flow maps until Branching MVP is tested: [Track a bug] might change [Track a feature] might change.

Previous Issue Card Flow Map:

6.4 Use Markdown

6.4.1 Write Markdown

Cheatsheet will go here.

6.4.2 Use Markdown Files

6.4.2.1 Add a Markfown File

6.4.2.2 Go to a Markdown File

6.4.2.3 Edit a Markdown File

6.5 Use GitHub Branches

6.5.1 Submit a Feature

6.5.1.1 Create a Feature Branch

6.5.1.2 Edit a Feature Branch

6.5.1.3 Test a Feature Branch

6.5.2 Run Quality Assurance

6.5.2.1 Orientation Map

6.5.2.2 Edit a Quality Assurance Branch

6.5.2.3 Test a Quality Assurance Branch

6.5.2.4 Merge a Quality Assurance Branch