fedora-infra / toddlers

#137 Dist-Git request processor always creates commit/branch in new repo/branch requests even when asked not to in request
Closed by zlopez. Opened by ngompa.

Closed
Reopen Issue

Repo and branch requests can be created with the option to not create the branch in Git. This could be done for various reasons. In the past, it was to avoid the commit adding the package.cfg file, but now it's mainly used for being able to push a package history when creating a new compat package or alternative version package.

My reading of the Dist-Git request processor toddler is that it ignores this case and will always create a repo with an initial commit or create a branch and sync the initial commit in.

Can someone please make sure that it works when the user requests it to not be created?

You are right. From what I remember we discussed this with @humaton and decided to always have default branch except for tests namespace.
I don't remember the exact arguments, but we can reintroduce this option if it will be needed again.

It is needed. Whenever compatibility packages are branched, I want this case to work so I can push the old history. Example: https://src.fedoraproject.org/rpms/python-sqlalchemy1.3/commits/rawhide

I'm looking at the fedscm_admin, which was used for processing the tickets before and it always creates initial branch as well, so we used the same logic in scm_request_processor.

So this was probably done completely manually in past.

I see that this option is available for new branch only, which is even in the automation.

Here https://pagure.io/releng/fedora-scm-requests/issue/50384 it worked like a charm.

Closing this as it's working as intended

Metadata Update from @zlopez:
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.