The koji clone-tag command will create an entirely new destination tag, but the "--help" text does not make this behavior obvious.
koji clone-tag
When we create our milestone product release composes, we clone a tag as one step in a larger process. The longer --help text will assist the process writers, and make it clear that admins do not need to pre-create the destination tag before cloning.
--help
I would think that the word "clone" implies the creation of a new thing. If anything, the confusing bit is that the command can also be used to sync content in a pre-existing tag.
Still, given that this command is confusing all around, I'm all for clarifying it.
Longer term, this command should probably be replaced, or at least supplemented, with a better defined and named command.
Metadata Update from @mikem: - Custom field Size adjusted to None
Metadata Update from @mikem: - Custom field Size adjusted to small (was: None) - Issue priority set to: Low (was: Normal) - Issue tagged with: doc
That was it exactly. We can make --help tell us how this command behaves in both scenarios: when A) the destination tag does not exist and B) the destination tag exists.
Metadata Update from @tkopecek: - Issue set to the milestone: 1.19 - Issue tagged with: easyfix
Metadata Update from @tkopecek: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
PR #1623
Metadata Update from @jcupova: - Issue tagged with: testing-done
Metadata Update from @dgregor: - Issue assigned to breilly
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/koji/issues/1509
Please continue any further discussion there.