I'd like to close https://src.fedoraproject.org/rpms/librsvg2/pull-request/17 , which is obsolete now. I am part of the @gnome-sig, which is an admin of the librsvg2, still I cannot do it, because when I click on the green Merge button at the top only an empty green box shows up:
@gnome-sig
I would also want to eventually merge the https://src.fedoraproject.org/rpms/librsvg2/pull-request/20 , but I cannot do that either. What am I missing?
For what it's worth, I've been able to merge https://src.fedoraproject.org/rpms/snapshot/pull-request/14 yesterday, where both packages have quite similar settings with respect of the membership.
This might be related: I am part of the https://accounts.fedoraproject.org/group/gnome-sig/ and I had been part of the https://src.fedoraproject.org/group/gnome-sig too, at least yesterday, but when I checked today, I had not been part of the later for whatever reason. When I re-logged to the src.fedoraproject.org I showed up in the later group too.
The question is: why had I been removed from the src.fp.o during the night?
The merge thing is a known bug... it shows it when you don't actually have permissions to merge. ;(
The removal thing I am not sure about. We do have some automated processes to remove people from groups, but only when they are no longer in the packager group, but you are still (and never have been removed from it that I can see). For further investigation of that can you file a fedora infra ticket? ( https://forge.fedoraproject.org/infra/tickets ).
This is the upstream pagure project, not concerned with deployments like src.fedoraproject.org
I'm still wondering how this happened. It can be due to me logging in in the other (main) browser. I do not know yet.
I had been added to the gnome-sig the last week. I've been there months ago, and removed, also months ago.
Upstream pagure, ah, right, I kinda expected the footer's "File an Issue", which leads here from the pull request link, was meant for that instance, not as a generic upstream ticket. I'm sorry, I did not pay enough attention to it.
Metadata Update from @mcrha: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)