developermetrics / lead-time-for-changes Goto Github PK

The documentation references deployment-frequency instead of lead-time-for-changes.. in

- name: Test another repo
  uses: samsmithnz/deployment-frequency@main
  with:
    workflows: 'CI/CD'
    owner-repo: 'samsmithnz/DevOpsMetrics'
    default-branch: 'main'
    number-of-days: 30

Hi!

I have a feature request/suggestion and wonder if it is possible to implement.

It would be great to be able to filter the PRs that are used to calculate the score by user names. In addition it would be nice if the label of the badge could be adjusted.

Background: I would like to measure the time it takes to merge only pull requests that were created by Renovat or dependabot. Thereby it would be possible to measure how long it takes to apply dependency updates to the main branch. Since this would not be the lead time for all changes, an adjustable badge label would help to reflect that the lead time only affects a subset of all pull request.

While I know this would not be exactly the lead time anymore, I can understand if you do not include this feature to the action. But since this action calculates exactly what I need for a subset of all pull requests I thought, I can at least ask if you see that as a useful addition to your action.

Thank you and best regards
m-ibot

• Add new script to calculate based on last 100 PR's
• Add docs to document usage
• Add tests to workflow
• Add versioning
• Add Auth
• #8

Looks like the appId, appInstallationId, and appPrivateKey are not getting passed to the getAuthHeader function, resulting in "No authentication detected"

https://github.com/DeveloperMetrics/lead-time-for-changes/blob/main/src/leadtimeforchanges.ps1#L47

Let me know if I overlooked something.

Thanks!

similar to https://github.com/samsmithnz/deployment-frequency#output