Dev: Update GH Actions to start the meter when the work comes in a sprint
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**Describe the task**
Update GH Actions to start the meter when the work comes in a sprint
**Acceptance Criteria - can we find a way to calculate the DORA Metrics?**
- [ ] Change Lead Time
- [ ] Deployment Frequency
- [ ] Change Fail Rate
- [ ] Failed Deployment Recovery Time
- [ ] Work in Progress
- [ ] Cycle Time
- [ ] Work Item Age
- [ ] Throughput
**Additional context**
- [Add any other context about the task here.](https://github.com/github/issue-metrics/blob/main/issue_metrics.py)
- https://bcgov.sharepoint.com/teams/02081/Shared%20Documents/Forms/AllItems.aspx?id=%2Fteams%2F02081%2FShared%20Documents%2FGeneral%2FScrum%20Kanban%20Flow%20Metrics%2Fflowmetricsforscrumteams%2Epdf&parent=%2Fteams%2F02081%2FShared%20Documents%2FGeneral%2FScrum%20Kanban%20Flow%20Metrics&p=true&ga=1
- 
Contributor guide
Research direction
Start by reading the linked issue_metrics.py and inspecting the repository’s existing GitHub Actions workflows. Determine how sprint entry can be identified and how each listed DORA and flow metric should be calculated, then define the outputs and checks that demonstrate all eight acceptance criteria are met.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- analytics, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100