Some KubeVirt org users report they can not edit their pull requests any more

[dhiller]

Select Topic Area

Question

Body

Hey, I am one of the GitHub KubeVirt org admins.

We have some users reporting that they can not edit their pull request subject and/or descriptions any more. This started yesterday.

I've checked temporary interaction limits and rulesets, both of which seem ok. I also looked at the audit log and could not find any configuration change on that matter.

We are not aware of any change from our side that could have caused this. We are using k8s peribolos for org, repo and team management with config file https://github.com/kubevirt/project-infra/blob/main/github/ci/prow-deploy/kustom/base/configs/current/orgs/orgs.yaml

Any ideas what else to do to debug this?

Thanks!
@dhiller

[Daniel-Ric]

This usually comes down to permissions, not a “GitHub UI” toggle. On GitHub you can edit a PR title/body only if you’re the PR author or you have at least triage/write access to the repo. If “some users” suddenly can’t edit, it often means their effective repo permission dropped (e.g. from triage to read) due to a team permission change or an automation sync (peribolos).

What I’d check to debug quickly:

Pick one affected user and one affected repo and verify their effective permission level (repo -> Settings -> Collaborators/Teams, or via the collaborators API). If it shows read, they won’t be able to edit PR metadata.

Check whether the PRs they can’t edit are authored by them or by someone else. If they’re trying to edit other people’s PRs, they need triage/write; read won’t be enough.

Review recent peribolos sync output / config changes that could have changed team-to-repo permissions (even if the audit log doesn’t make it obvious). A small change like removing a team from a repo or changing a team permission from triage to read would match this symptom.

As a workaround, grant the affected team triage (or write) on the repo and re-test. If that fixes it, you’ve confirmed it’s a permission regression.

[dhiller]

None of these yielded a result - however I have another interesting update. One user reported that using the gh cli worked for them:

FWIW gh pr edit 16582 --title "Add CentOS Stream 10 build support" just worked for me on kubevirt/kubevirt#16582

[dhiller]

Tried for a specific user, following query didn't yield anything: repo:kubevirt/kubevirt user:orelmisan -action:pull_request.close -action:pull_request.create_review_request -action:pull_request.create -action:pull_request.merge -action:pull_request.ready_for_review

Something else I've tried was created:>=2026-02-03 action:team.create action:team.destroy action:team.add_member action:team.remove_member action:team.promote_maintainer action:team.demote_maintainer and it didn't yield anything either.

Looking at the peribolos logs didn't reveal anything either.

I am out of ideas right now.

[Daniel-Ric]

Oh - well then im lost as well haha

[dhiller]

@Daniel-Ric thanks a lot for your help anyway, highly appreciated! 💪 💯

[dhiller]

It seems others are experiencing this too: https://github.com/orgs/community/discussions/186398

[dhiller]

This looks like a UI error, feedback posted https://github.com/orgs/community/discussions/186398