Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[New Feature]: Have GitOps do the pipeline status badges instead of wingetbot #242835

Open
Trenly opened this issue Mar 27, 2025 · 1 comment
Open

[New Feature]: Have GitOps do the pipeline status badges instead of wingetbot #242835

Trenly opened this issue Mar 27, 2025 · 1 comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Triage This work item needs to be triaged by a member of the core team.

Comments

@Trenly
Copy link
Contributor

Trenly commented Mar 27, 2025

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
@Trenly Trenly added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Mar 27, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage This work item needs to be triaged by a member of the core team. label Mar 27, 2025
@Trenly Trenly mentioned this issue Mar 27, 2025
Merged
2 tasks
@Trenly Trenly changed the title [New Feature]: Have GitOps do the validation labels instead of wingetbot [New Feature]: Have GitOps do the validation status labels instead of wingetbot Mar 27, 2025
@Trenly Trenly changed the title [New Feature]: Have GitOps do the validation status labels instead of wingetbot [New Feature]: Have GitOps do the pipeline status badges instead of wingetbot Mar 27, 2025
@DuckDuckStudio
Copy link
Contributor

Image
Two same comments. XD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Triage This work item needs to be triaged by a member of the core team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Trenly @DuckDuckStudio