Highlight invalid testing output in suite_report.py
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 42/100
Research direction
Start by reading suite_report.py and locate where warnings about uncommitted changes are produced. Make those warnings visually more obvious, then verify that the invalid testing output is clearly highlighted without changing the warning content.
Written by the indexing model from the issue text.
Description
It has been suggested that the warnings about uncommitted changes in suite_report.py should be highlighted in a more obvious way, possibly using coloured text?
- 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
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
learningequality/ricecooker#747 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BSData/horus-heresy-3rd-edition#3171 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
run-llama/llama_index#23199 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
KhronosGroup/glTF-Blender-IO#2769 ·