Learn more about these different git repos.
Other Git URLs
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.
.gitignore
sources
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.
fedpkg import
fedpk import
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.
--allow-unrelated-histories
I'd like to request 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.
fedpkg request-repo
--no-initial-commit
initial-commit: false
Thanks.
This originated at https://pagure.io/fedora-infrastructure/issue/6651
FWIW, when requesting a branch, you can use the --no-git-branch flag. This doesn't help with the master branch but it helps with all the others.
--no-git-branch
master
See also https://pagure.io/fedpkg/issue/149
Metadata Update from @cqi: - Issue set to the milestone: 1.34
Metadata Update from @cqi: - Issue tagged with: RFE
Metadata Update from @cqi: - Issue assigned to cqi
PR: https://pagure.io/fedpkg/pull-request/240
Waiting for https://pagure.io/fedscm-admin/issue/1 to be fixed.
Metadata Update from @cqi: - Issue set to the milestone: NEXT (was: 1.34)
Metadata Update from @cqi: - Issue tagged with: partner
Fix to https://pagure.io/fedscm-admin/issue/1 is included in https://bodhi.fedoraproject.org/updates/fedscm-admin-1.0.2-1.fc28.
Metadata Update from @cqi: - Issue set to the milestone: 1.35 (was: NEXT)
Commit 857823e fixes this issue
Login to comment on this ticket.