Create pattern-metrics.yaml

[zkoppert]

Getting started measuring pattern metrics. Related to #565.

This pull request implements

• Time to first response metrics for new issues (excluding codeowners created) recurring every month
• Time to first response metrics for new pull requests (excluding codeowners created) recurring every month

cc/ @spier

[zkoppert]

I did some local testing of the parts and pieces in these workflows and it does seem to work. Next I'll work on getting metrics on,

• number of new Structured patterns
• number of new Initial patterns
• number of new Known Instances for an existing pattern

[zkoppert]

@spier Any idea what happened on the failing GitBook Generation? Maybe a permissions issue?

[spier]

@zkoppert the issue is likely still related to issue #581.
For the time being we can just ignore those failing Gitbook generations.

[spier]

@zkoppert thank you for this PR!

I was going through your code, trying to understand how it works, and what it does.

Where I got stuck was that I don't see the issue_metrics.md file mentioned in the GHA in this PR.
Is it missing? Or does it get created by something else that I don't see here?

Thanks again for helping us collect helpful metrics about the way that contributions work on this repo.

[spier]

Ah, I think I see it now in the docs:
https://github.com/marketplace/actions/issue-metrics

The github/issue-metrics@v2 step is creating the issue_metrics.md file, right?

[zkoppert]

Ah, I think I see it now in the docs: https://github.com/marketplace/actions/issue-metrics

The github/issue-metrics@v2 step is creating the issue_metrics.md file, right?

Yup, that is exactly it. The issue_metrics.md file gets created by the github/issue-metrics action.

[spier]

@zkoppert if you like, you can pull from main again. I made the CODEOWNERS file a bit simpler, so you will have less clutter in there when extracting the info from there via your script.

[spier]

From what I understand the GHA creates one issue for each "report type".

e.g.

• issue (1) "Monthly New Issues Data 2023-10-01..2023-10-31"
• issue (2) "Monthly New Pull Request Data 2023-10-01..2023-10-31"

I left some other comments inline, mostly to understand better how this works.

I am happy to merge this, so that we can try it out.

Would we run in once manually, so that the first reports are generated immediately?

[spier]

@zkoppert should I go ahead and merge + run this GHA already as a first test "in Production"? :)

[zkoppert]

@spier yes, that sounds good!