Expanding project reporting functionality
@cameronbateman-mo ci sta già lavorando.
Dal 6/3/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
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.
- Lingua principale
- Python
- Stelle
- 9
- Fork
- 19
- Merge medio
- 5g 48m
- PR unite (30g)
- 4
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di MetOffice/SimSys_Scripts
-
enhancement
MetOffice/SimSys_Scripts#240 · 1 commento · 1 assegnatario ·
-
MetOffice/SimSys_Scripts#235 · 9 commenti · 1 assegnatario ·
-
MetOffice/SimSys_Scripts#221 · 1 assegnatario ·
-
bug
MetOffice/SimSys_Scripts#220 · 1 assegnatario ·
-
enhancement
MetOffice/SimSys_Scripts#217 · 4 commenti · 1 assegnatario ·
Tutte le issue di MetOffice/SimSys_Scripts
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100