There is no documentation on how to suppress warning annotations that occur in files not modified in a given pull request
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
The document at https://github.com/actions/toolkit/blob/master/docs/problem-matchers.md makes no mention of how to suppress warnings that occur in files not modified in a given PR. If this feature is not yet available, it should be made available (either on a per-matcher or, perhaps, a per-repository basis) and there should be documentation about how to accomplish this.
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
Start with docs/problem-matchers.md and review its current description of warning annotations. Determine whether suppression for files outside a pull request's changes already exists; if not, clarify the requested per-matcher or per-repository behavior and document the supported outcome. There are no tests or implementation files named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100