I would like to volunteer to help again with processing of fedora-scm-requests.
While I don't claim that I will be able to do this daily - I have noticed there are days when processing doesn't happen - I can certainly help when the queue builds up and also I am based in APAC, a different timezone to the other admins, which helps to spread the load and expedite requests in some cases.
I have done this role in the past (long before pagure).
I am not sure which FAS group this corresponds to now and I hope it is okay to post the request here? (I couldn't find any pointers)
Wow I managed to get issue 10000 :-)
Congrats! You win!
:grinning:
Anyhow, no objection from me, but right now things are in a bit of flux, as we need to fix fedscm-adm for recent changes.
Congrats! You win! :grinning: Anyhow, no objection from me, but right now things are in a bit of flux, as we need to fix fedscm-adm for recent changes.
:thumbsup: for me (on both points)
Metadata Update from @siddharthvipul1: - Issue tagged with: low-trouble, medium-gain, ops
Hi, @petersen so you need to set up your local environment as in the README file in fedscm-admin repository. Then just run fedscm-admin processall to process all tickets in fedora-scm requests repo.
Thanks, just noticed this finally
But I don't see myself listed in members or any new fas group for this yet? Or I just need the tokens?
FYI, I've documented how to create the pagure API token for src.fp.o so that more people can create them as needed: https://pagure.io/fedora-infra/howtos/c/fa23906fe6622831577f57df45561367a82e9893?branch=main :)
Thanks, I opened https://pagure.io/fedscm-admin/pull-request/67 to clarify this step.
I don't have permission to https://pagure.io/releng/fedora-scm-requests/token/new :
Forbidden You are not allowed to change the settings for this project
@mohanboddu I think I need to be added to https://pagure.io/releng/fedora-scm-requests/ members?
@petersen is now admin of https://pagure.io/releng/fedora-scm-requests/
Thank you
Seems I also need pdc permissions?
nirik helped me - so hopefully all good now - will test on the queue tomorrow
Metadata Update from @petersen: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)