This is based on a quick git grep and quite un-tested. The test suite fails for me in tox as well as when running nosetests manually :(

I added more changes, but this also needs changes to tests.

These changes to tests are sufficient to make them pass locally for me.
https://pagure.io/fork/lsedlar/fedpkg/c/6f9b0667800b8fad5fcec2afde2617f8c8e9d0fe?branch=fix-review-424

Is the tooling that handles new branches updated to handle requests for rawhide branches? This patch would change the JSON that is submitted to list rawhide instead of master.

These changes to tests are sufficient to make them pass locally for me.
https://pagure.io/fork/lsedlar/fedpkg/c/6f9b0667800b8fad5fcec2afde2617f8c8e9d0fe?branch=fix-review-424

I've enabled PRs on my fork so you can open a PR against my fork ;-)

Is the tooling that handles new branches updated to handle requests for rawhide branches? This patch would change the JSON that is submitted to list rawhide instead of master.

It's on the todo @humaton and @mohanboddu should be looking at this iirc

considering the state of these two projects, I doubt we'll change their default branches

FTR I didn't mean the default branch of the request repo itself, but the content of submitted requests:
https://pagure.io/releng/fedora-scm-requests/issue/31722
With this patch, branch would switch from master to rawhide, which is probably a wanted change, and I just want to make sure tools processing the ticket can handle it.

Isn't this should be rawhide as well and while we are at it, better change the test name as well.

Maybe keep this one as is as it shows the backward compatibility and add a new one?

Maybe keep this one as is as it shows the backward compatibility and add a new one?

Sounds good to me.

Looks all good to me! :)

Code looks correct. Tests are also passing. Don't know why they were not exected automatically, but I run Jenkins manually. I took a patch to build fedpkg scratch build. I tried at least building functionality from dist-git branch which has old master branch. It worked.
My only concern is whether fedora-scm (already) creates rawhide branches for fedpkg requests. Will they create "symlink" branches or just a single one?
There are 4 commits in the PR. They look complicated because at least first two commits are interfering together. The best approach for me would be 2 commits for functionality and unittests. If you don't mind, I can try to transform it during the merge. I would like to preserve authors (in case of 2 authors, I would name one of you in the commit message).

OK, answering to myself :)
https://fedoraproject.org/wiki/Changes/GitRepos-master-to-main:
Along with the src.fedoraproject.org changes, we will update the branch filter list and forbid 'master' from being pushed at all. Additionally, we will establish a sym-ref between 'rawhide' and 'main' as a convenience for people who prefer to use 'main' branch for rawhide.

My only concern is whether fedora-scm (already) creates rawhide branches for fedpkg requests. Will they create "symlink" branches or just a single one?

@humaton @mohanboddu do you know the status of fedscm-admin?

My only concern is whether fedora-scm (already) creates rawhide branches for fedpkg requests. Will they create "symlink" branches or just a single one?

@humaton @mohanboddu do you know the status of fedscm-admin?

fedscm_admin creates the main "symlink".

fedscm_admin creates the main "symlink".

And can handle new package/branch requests asking for "rawhide" instead of "master"?

Commit 34a971b2 fixes this pull-request

Didn't find where the fedora-scm-request execution code resides, so I hope it is working as expected.
I regrouped 4 commits - resulting in 2. And I am going to create and release a patch.
Thank you for the code, guys.

All fedpkg updates are listed here:
https://bodhi.fedoraproject.org/users/onosek