Git/CI Telemetry v3.1
PM360 connects directly to your team's Git repository to infer real progress from development activity.
Supported Providers
- GitHub (REST API v3 + webhooks)
- GitLab and Bitbucket support planned
What's Tracked
| Signal | Source | What It Shows |
|---|---|---|
| Commits | Push events | Development activity per task (tagged by ticket ID) |
| Pull Requests | PR events | Code reviewed and integrated |
| CI/CD Runs | Workflow events | Tests passing, coverage percentage |
| Deployments | Deployment events | Code deployed to UAT/staging/production |
Ticket Tagging
Commits and PRs are linked to PM360 tasks via ticket IDs in the message or title. Default format: PM360-{taskId}.
Example: PM360-123: Fix authentication bug → linked to Task 123.
Tagging Discipline
The telemetry layer depends on contractors tagging their commits with ticket IDs. If tagging rate drops below 70%, PM360 shows a warning: "Low ticket tagging discipline — progress triangulation will be unreliable."