On Wed, 19 Aug 2020, Christopher wrote:
So, just to be absolutely clear... I can remove the file, just do
epel8 as normal, and completely ignore the epel8-playground branch
forever?
As best as I can tell, yes. I have at least one package in epel8 that
doesn't have the package.cfg and it works okay. It just doesn't build
stuff automatically on epel8-playground. You might get bug reports from
people who have epel8-playground enabled and can't install your package
though.
You might get wider input on this on the epel-devel mailing list.
Also, I think there is some plan in the works to change how
epel8-playground works.
Can I have the extra commit that added the file removed by
force-pushing the prior commit, so it's easier to fast-forward merge
my 'master' branch onto epel8 without doing a bunch of crazy git merge
nonsense so they have the same HEAD commit?
I don't think you can force-push to dist-git so unfortunately you're stuck
with that commit forever. There *is* a way to get your branches created
without that commit in the first place, but it's too late for that now.
Can I have the epel8-playground branch removed? I never wanted it. I
know I can just ignore it and never check it out locally... but...
it's going to bug me being there on the remote.
Nope, you can't remove branches on dist-git.
Scott
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
