Add script to perform summary of merged PRs and closed issues

[registerrier]

Description

This pull request proposes a script to query the GitHub list of closed PRs and issues to list all merged PRs and count closed issues with a given milestone.

Usage:

python dev/github_summary.py  merged_PR 1.0 --token XXXX
python dev/github_summary.py  closed_issues 0.20 --token XXXX --print_issues True

It requires to install PyGithub (https://github.com/PyGithub/PyGithub)
Dear reviewer

[adonath]

@registerrier Be default I included the dev scripts in the CI check as well, just because they don't change often. However I'm not sure the dev scripts are included in the pre-commit hook. Maybe you can check and adapt the PR...

[codecov]

Codecov Report

Merging #4125 (8793690) into main (7a4a6f0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #4125   +/-   ##
=======================================
  Coverage   94.96%   94.96%           
=======================================
  Files         221      221           
  Lines       31445    31445           
=======================================
  Hits        29862    29862           
  Misses       1583     1583           

Impacted Files	Coverage Δ
gammapy/maps/core.py	85.82% <ø> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[registerrier]

@registerrier Be default I included the dev scripts in the CI check as well, just because they don't change often. However I'm not sure the dev scripts are included in the pre-commit hook. Maybe you can check and adapt the PR...

It is included in the pre-commit hooks. I was not executing them :).

[bkhelifi]

Thanks @registerrier, great implementation.
I have two thoughts:

• the functionality provided by the click function list_merged_PRs is the same than the one used to build a contributor list. I am wondering if it should not be into a dedicated function into a dev/utils.py... such that one can re-use it
• this nice implementation with PyGitHub provides the same type of information than git shortlog --merges --since XX --until YY. Do I mistaken? If yes, what are the pros and cons of each method?

[adonath]

It would be good to have something like this, but we should try to improve the implementation.

[registerrier]

The code has been completely changed. It now consists in a a general class GitHubInfoExtractor which deals with the github interface (login, token, repo) and whose main method build a summary table of PRs.
This table is then parsed by a helper function to produce an output list of PRs, the list of contributors (for now based on the list of people who opened the PRs).

It is called this way:

• to create the table

python dev/github_summary.py  create_pull_request_table --token XX  --number_min 3900 --overwrite True 

• to create the summary output

python dev/github_summary.py  merged_PR table_pr.ecsv 1.1 v1.0.1 v1.0.2

[adonath]

Thanks a lot @registerrier, I have no comments! This is a very useful and cleanly written script!

[AtreyeeS]

Thanks @registerrier !

[AtreyeeS]

Github counts from 1, so I guess the default number_min = 1