Project Issue / PR Metrics

[mikaelacaron]

Description

• I saw this blog post that uses GitHub actions to create a report of how many issues / PRs are opened and merged.
• I think it would be super cool to see metrics like this for each week of Hacktoberfest!
  • It could be a markdown file that's created, and then I could post in Discussions, it's fine if I have to run this manually (that may actually be preferred too)

Describe alternatives you've considered

• Later on this could turn into a weekly or monthly action that's run, depending on how busy the project is by the end of Hacktoberfest
• You may need to make a custom script for your own repo, and later let @mikaelacaron know what's needed to actually fill in the secrets / repo information to actually analyze the Basic Car Maintenance repo

Additional context

• It would be interesting to see metrics like this example from the article

[sirish123]

Could u assign this to me!

[mikaelacaron]

Go for it! Let me know if you need anything from me, to be able to read my repo, but you might be able to make a prototype on your own fork

[mikaelacaron]

Thank you for wanting to contribute!

I'm going to un-assigning you from this issue because it hasn't been updated in 3 weeks days, and there's only 2 days left in Hacktoberfest, and I want to allow others to be able to contribute to the project

[anupdsouza]

Hey @mikaelacaron, I'd like to take a look into this.

[mikaelacaron]

@anupdsouza Go for it! Thanks!

[mikaelacaron]

Attempted to run, but failed, details:
https://github.com/mikaelacaron/Basic-Car-Maintenance/actions/runs/10089980810/job/27898454351

PR #278 is when this code was merged in, but didn't work on the first run

[mikaelacaron]

I've figure it out over several commits how to make a single report for issues / PRs that are opened, and then another report for issues / PRs that are closed, because their action doesn't support the "and" operator to be able to combine everything yet