Copied from https://pagure.io/fedrepo_req/issue/140

When a new src.fp.o repo is created, there is always a first commit. It used to be Initial setup of the repo with empty .gitignore and sources, now it appears to be Added the README by @limb.

Based on the official instructions, fedpkg import is used to get the spec + patches to git and sources to the lookaside cache. A call to fedpk import just removes such README. It have been there exactly one commit and it's gone.

A packager with more complex workflow might prep the package in git (on pagure, or github or whatever). Once the package is approved, the maintainer wishes to merge the git history from the preparatory place into Fedora master. However a merge commit with --allow-unrelated-histories has to be created because of the pointless initial README commit.

I've requested an opt-in for fedpkg request-repo to indicate I don't want initial commit in the repo, such as for example --no-initial-commit. That could then add such option to the json posted at fedora-scm-requests, for example initial-commit: false. This was implemented.

Here I'd like to request that fedrepo_req-admin honors such flag and does not create the initial commit if the option is set to false.

Thanks.

This originated at https://pagure.io/fedora-infrastructure/issue/6651