Create issue-metrics.yml

[vikrampm1]

Description of the Change

This PR adds a GitHub Action to pull monthly metrics such as "Time to response","Time to close","Time in label" etc. into a new GitHub issue. Reference: https://github.com/github/issue-metrics.

Closes #

How to test the Change

Changelog Entry

Dev - Added a new GitHub action to pull monthly metrics.

Credits

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added tests to cover my change.
• All new and existing tests pass.

[jeffpaul]

This is great, let's get this in and see what the results look like. One thing we should consider is whether we want:

1. to run this action in all the repos we want to track with results stored in each repo
2. to run this action in all the repos we want to track with results stored in the .github repo
3. to run this action in the .github repo and referencing all the repos we want to track with results stored in each repo
4. to run this action in the .github repo and referencing all the repos we want to track with results stored in the .github repo

[jeffpaul]

I'm not sure if this needs the -reason:"not planned" flag, but we can run this and see what happens.

[jeffpaul]

Leaving the https://github.com/github/issue-metrics/blob/main/docs/example-workflows.md#multiple-repositories-example reference here in case we want to consider options 3 or 4 above

[jeffpaul]

Seeing that the two test runs I did here: #241, #242. If we keep these metrics within the individual repos (and not in the .github repo), then it would be awesome if the action would add the monthly metrics as a comment on an existing issue (perhaps as a variable in the workflow file so that we could link directly to a 2024/2025/etc metrics issue) and then pin that issue in the repo.

It would be helpful to give this a try in the .github repo pulling in 2-3 OSP repos to see how it looks there, curious if that data goes into a single issue or not and how well it delineates the names of the repos in that content.

[vikrampm1]

Seeing that the two test runs I did here: #241, #242. If we keep these metrics within the individual repos (and not in the .github repo), then it would be awesome if the action would add the monthly metrics as a comment on an existing issue (perhaps as a variable in the workflow file so that we could link directly to a 2024/2025/etc metrics issue) and then pin that issue in the repo.

Yea, if we can able to achieve that scenario then I think that would be great. From reading the instructions on the repo page I think it'll only create a new issue every time it runs (for the time frame we set).

It would be helpful to give this a try in the .github repo pulling in 2-3 OSP repos to see how it looks there, curious if that data goes into a single issue or not and how well it delineates the names of the repos in that content.

We can try this and see how that works out.