Expanding project reporting functionality
@cameronbateman-mo is already working on this.
Since Mar 6, 2026.
Assessment
This issue has not been assessed yet.
Description
Once finish_milestone.py has been run all the PRs are archived from the project. In order to easily gather statistics about a release its therefore good to gather that information as part of the script. There is currently a short reporting function that prints the number of pull requests by repo to the terminal while running which can be expanded and modified.
Questions:
- What is the best format for storing these statistics? A spreadsheet was put together for 2026.03.1 to manually record the data before the archiving was done. Follow this principle?
- Is this functionality only needed after the release (and can therefore be part of finish_milestone.py), or would it be nice to run mid-release to gather information (e.g. for a presentation or meeting) and therefore should be a standalone script that can be called by finish_milestone.py?
- What details need to be gathered? The 2026.03.1 caught assignees, reviewers, repos and labels. Is this all?
Breakdown:
- In finish_milestone.py modify the report to store the current repository data to a suitable file
- Update review_project.py so that all details required are extracted from the raw json
- Add functions to aggregate those statistics nicely (there are routines for counting items but they are limited at the moment)
- Expand report funtions to cover the extra stats
- Move report functionality to its own file if wanted
- Investigate no error being thrown when permissions for archiving are not set correctly for the user of the script.
- Dominant language
- Python
- Stars
- 9
- Forks
- 19
- Avg merge
- 5d 48m
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MetOffice/SimSys_Scripts
-
enhancement
MetOffice/SimSys_Scripts#240 · 1 comment · 1 assignee ·
-
MetOffice/SimSys_Scripts#235 · 9 comments · 1 assignee ·
-
MetOffice/SimSys_Scripts#221 · 1 assignee ·
-
bug
MetOffice/SimSys_Scripts#220 · 1 assignee ·
-
enhancement
MetOffice/SimSys_Scripts#217 · 4 comments · 1 assignee ·
All issues in MetOffice/SimSys_Scripts
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100