github-community-projects / github-community-projects/issue-metrics
Time from Approved to Closed
- Dominant language
- Python
- Stars
- 538
- Forks
- 94
- Avg merge
- 49m
- Merged PRs (30d)
- 13
Description
### Is your feature request related to a problem?
In our workflow we create PR when we think a feature is ready.
This will then create a Vercel preview URL.
Once the PR has been approved by a dev, it will go over to manual QA.
Once approved by the QA, we merge in to main which deploys to prod.
It would be useful to know what is holding up PRs. Approval or manual QA.
### Describe the solution you'd like
I would like to see some additional metrics around time from PR Open to Approval and Approval to PR Close.
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.