Learn more about these different git repos.
Other Git URLs
I attempted to update each branch that is missing it, but the issues opened were autoclosed:
$ fedpkg request-branch 1.20 --sl bug_fixes:2022-12-01 https://pagure.io/releng/fedora-scm-requests/issue/46455 https://pagure.io/releng/fedora-scm-requests/issue/46456 https://pagure.io/releng/fedora-scm-requests/issue/46457 $ fedpkg request-branch 1.21 --sl bug_fixes:2022-12-01 https://pagure.io/releng/fedora-scm-requests/issue/46458 https://pagure.io/releng/fedora-scm-requests/issue/46459 https://pagure.io/releng/fedora-scm-requests/issue/46460 $ fedpkg request-branch 1.23 --sl bug_fixes:2023-06-01 https://pagure.io/releng/fedora-scm-requests/issue/46461 https://pagure.io/releng/fedora-scm-requests/issue/46462 https://pagure.io/releng/fedora-scm-requests/issue/46463
What's the right way to update the branches so they EOL correctly?
When do you need this? (YYYY/MM/DD)
When is this no longer needed or useful? (YYYY/MM/DD)
If we cannot complete your request, what is the impact?
Metadata Update from @kevin: - Issue tagged with: low-gain, low-trouble, ops
Hi @haircommander, this is probably an issue with our cryptic messaging from the tool we use to process SCM requests. The branches you requested were created and are in fact visible in the PDC api https://pdc.fedoraproject.org/rest_api/v1/component-branch-slas/?branch_type=module&global_component=cri-o
ah hah, excellent to hear! thanks
Metadata Update from @haircommander: - Issue close_status updated to: It's all good - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.