A demo and some documentation for using GitHub as our project management tool.
- Teams: groups of GitHub users related to a specific project or task. Teams can be nested, and have discussions built into them.
- Issues: document a bug, get help, ask a question. Pretty much any reason!
- Labels: categorize issues, discussions and project board items to keep the project organized and on track.
- Discussions: get questions and input from your user base, discuss ideas for new features, clarify documentation.
- Project Boards: automated kanban; bug triage; really any project planning
- Wiki: long form documentation about your project including contribution rules, best practice guidelines, demo content.
-
Organization: e.g., bhklab
- Top level grouping for our lab; all lab members are in the organization
- Teams within an organization to specialize people for specific tasks
- Teams have their own discussion and project boards
- Teams can be assigned broader permissions within a repository
-
Repo: e.g., CoreGx
- Can be administrated by individual users or by teams
- Have Issues, Labels, Discussions (if you enable them), Project Boards and a Wiki
-
Organization level PM tasks:
- Aggregate cross repository tasks
- For project managers, big picture staff
-
Repo level PM taks:
- Organize issues into work items in your kanban board
- Use automated kanban to close issues with Pushes or Pull Requests