Implement coherent summarizing of revision/build/test status
Open
- Dominant language
- Python
- Stars
- 26
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Right now we have disparate status values across revisions/builds/tests, and we don't have a uniform way to summarize them onto one value, saying e.g.: "this revision is OK", accumulating all the build and test statuses.
Come up with the logic and the terminology to summarize those.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting the repository's existing revision, build, and test status values and their data definitions. Define the terminology and aggregation rules for one coherent summary value, with completion marked by a consistent status model that can express the combined outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100