viable/strict updating silently broken
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17.9k
- Forks
- 7.3k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 13
Description
🐛 Describe the bug
See https://github.com/pytorch/vision/actions/runs/26477016130/job/77965081560; the update bot doesn't have permissions for this repo, but the error doesn't show up in the job status.
Versions
N/A
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 the linked GitHub Actions run, job 77965081560, and inspect the viable/strict update workflow. Reproduce the update bot's missing-permission failure and trace how that failure is reported in the job status. Done means permission errors are visible rather than silently treated as successful.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100