microsoft / microsoft/winget-pkgs
[New Feature]: Have GitOps do the pipeline status badges instead of wingetbot
Open
Nobody has claimed this yet.
Area-Validation-Pipeline
Issue-Feature
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
Description of the new feature/enhancement
Wingetbot has different rate limits than GitOps. The policy service can easily handle commenting the pipeline status badges which will save on wingetbot rate limits, which can then be used for other tasks like PR validations
Proposed technical implementation details (optional)
No response
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 tracing how GitOps and the policy service currently publish pipeline status badges, then compare that with wingetbot's current responsibility. Confirm the ownership and rate-limit requirements with maintainers; done means GitOps handles the badges while wingetbot no longer does, with the resulting comments validated.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100