LouisBrunner / LouisBrunner/checks-action
Checks and Workflows conclusion can be different (+ Checks UI is confusing)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 277
- Forks
- 64
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 3
Description
Neither annotations nor job conclusion seem to be working as expected.
If you look at this job run: https://github.com/LouisBrunner/checks-action/actions/runs/220658890
Note that the example annotations are not shown, and that tests like "test_basic_failure" and "test_basic_neutral" just show as successful.
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.
Research direction
Start with the linked job run and the test_basic_failure and test_basic_neutral cases, then compare the annotations and conclusions they produce with what the Checks UI displays. Done means identifying and correcting the mismatch so annotations appear and the tests report their intended conclusions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, github-actions, typescript
- Domain
- api, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100