Verified program status for GitHub
Engineering teams that plan in GitHub Issues and Projects stay there. Tarivra reads the program issues and their sub-issues, checks the reported status against them and puts GitHub programs in the same portfolio view as the rest.
Connecting GitHub
Your GitHub admin installs the Tarivra GitHub App on the repositories you choose. Its tokens last an hour and renew themselves, so there is nothing to rotate by hand.
- Issues: Read, plus Read and write only if decisions should be written back
- Metadata: Read and Projects: Read
- No Contents, Administration or all-repository access
What becomes a program
A team adds the tarivra-program label to an issue. Its sub-issues, two levels deep, are the program's work.
- Status comes from the GitHub Project's Status field when the issue is on one, else from open or closed
- The milestone's due date is the target; the first assignee is the owner
- A rag-green, rag-amber or rag-red label gives the declared status
What Tarivra reads
Tarivra never reads source code, attachments or anything outside the projects, repositories and tables you grant.
- Issue titles, states and Project status, and when each was opened, updated and closed
- Assignees and milestones
- A blocked label; issues closed as not planned are left out
- Links in other tools that point to a GitHub issue, for dependencies across tools
How the status is checked
Tarivra compares the status the team reports with what the work shows, runs these checks and scores how well the two agree.
- ScheduleIs the work finishing fast enough to make the target date?
- Scope growthHow much work was added after the start?
- ThroughputIs the team finishing work at a steady pace?
- Overdue workHow much is past its due date?
- Blocked workHow much is flagged or marked blocked?
- Stale workIs in-progress work sitting untouched?
Connect ServiceNow as well to add change health: whether recent changes failed or caused incidents.
Decisions that stick
An approved decision becomes an issue added as a sub-issue of the program, labeled tarivra-decision and assigned to the action owner when exactly one person matches. The decision closes in Tarivra when the issue is closed.
This is the only thing Tarivra writes, and only if you allow it. Every decision is also kept in an audit log nobody can edit.
Questions
Can Tarivra read our source code?
No. The GitHub App asks for Issues, Metadata and Projects only. It has no Contents permission, so code, pull request diffs and files are out of reach.
Does it work with GitHub Enterprise Server?
Tarivra connects to GitHub.com, including GitHub Enterprise Cloud organizations. If you run GitHub Enterprise Server, tell us your version when you request a demo.
We do not use GitHub Projects. Will it still work?
Yes. Without a Project, an open issue is to do and a closed one is done, and a blocked label still marks blocked work.