Consider breaking out build/test summaries
Open
@mrbazzan is already working on this.
Since Mar 9, 2023.
good first issue
- Dominant language
- Python
- Stars
- 26
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
At the beginning of each notification we have a summary of checkout/build/test status. E.g.:
OVERVIEW
Builds: ❌ FAIL
Tests: ❌ FAIL
Later in the message we break those down by status. E.g.:
BUILDS
Status
❌ 83 ✅ 1065
and
TESTS
Status
❌ 23 ✅ 17 ⏩ 32 🚧❌ 1 🚧✅ 1 🚧⏩ 9
However, since we have so many failures, a lot of which are false positives, we should consider duplicating the breakout at the introductory overview as well. I.e.:
OVERVIEW
Builds: ❌ 83 ✅ 1065
Tests: ❌ 23 ✅ 17 ⏩ 32 🚧❌ 1 🚧✅ 1 🚧⏩ 9
This would let the readers get a feeling for the results faster.
Suggested by @broonie.
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.