microsoft / microsoft/winget-pkgs
[Pipeline Bug]: Pipelines ignore existing waiver labels, and instead re-instate the waivered labels.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 616
Description
There's been a plural amount of cases recently where an admin gave a PR the Waived-Validation-No-Executables label, then the pipeline immediately restarted, and when the pipeline finished it'd remove Waived-Validation-No-Executables and re-add Validation-No-Executables.
Recentmost case that I know of:
- #375599.
Proposed solution
Make pipelines acknowledge waivers.
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 by examining the pipeline behavior reported in issue #375599 and trace how validation labels are updated when a pipeline restarts. Done means an existing Waived-Validation-No-Executables label remains in place and the corresponding Validation-No-Executables label is not re-added after the pipeline finishes.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100