Open soininen opened 2 days ago
I think the current behaviour is that you have to repeat the --exclude <pkg>
argument also for publish
. But you are right in not expecting that, since pkgtags.json
clearly specifies which packages to release.
conduct publish --help
does not mention the --exclude
flag so I though it would pick the packages automatically from pkgtags.json
in any case.
Oh! That's a double bug then!
Does it even make sense to have --exclude
in publish
? What happens if you exclude packages that you did not exclude when running release
?
I think this isn't actually deliberate. When I fixed #22 I think what I did (I don't remember the details any more :stuck_out_tongue:) was incorporate the --exclude
or --only
flags into the config file parsing. I think that is why it expects the flags to be repeated because the config file has all packages defined.
You are right of course, the correct behaviour should be,
pkgtags.json
for pkg in json: pkg in config
But the common flags not showing in the help message may still be a bug, but irrelevant for the proper solution for the original problem of this issue.
I created new releases while skipping
spine_items
:When trying to publish with
encountered this Traceback: