microsoft / microsoft/winget-pkgs

Policy bot sometimes doesn't add status comments

Open
#162,847 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Bots Issue-Bug
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

See open PRs (that have a label applied) through this filter

https://github.com/microsoft/winget-pkgs/pulls?page=2&q=is%3Apr+is%3Aopen+-commenter%3Amicrosoft-github-policy-service%5Bbot%5D

These are all PRs where the policy service bot didn't add a status comment. Usually when status labels are applied on a PR e.g., Internal-Error, Validation-Completed or others, the bot adds a comment explaining the context behind applied label, which isn't happening in these cases.

(For reference, https://github.com/microsoft/winget-pkgs/pulls?q=is%3Apr+is%3Aopen+commenter%3Amicrosoft-github-policy-service%5Bbot%5D shows PRs where bot correctly adds these comments)

comment: <[Policy] Issue-Bug>

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Use the two linked GitHub pull-request filters to compare PRs where status labels such as Internal-Error or Validation-Completed were applied. Identify why the policy service bot comments on some labeled PRs but not others; the issue is done when the affected open PRs consistently receive the expected status-context comments.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
devops
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.