ctrf-io / ctrf-io/github-test-reporter
Feature: `on-fail-only` only for new comments
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 376
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
We wanted to enable on-fail-only to reduce noise in PRs. We currently use overwrite-comment for the same reason.
Unfortunately we've noticed that after a test failure and subsequent posting of a comment on the PR with failures, a successful build does not update or remove the comment indicating failures despite there no longer being any failures.
Would it make more sense to change on-fail-only to apply only to posting a new comment and not for updating/overwriting existing comments?
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.
Research direction
No file or test entry point is named. Start by locating the handling for on-fail-only and overwrite-comment, then trace how new comments differ from updates or overwrites. Done means a successful build updates or removes an existing failure comment while on-fail-only still prevents a new comment when there are no failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100