Forgetting to add is_other_project to results in some strange behavior

[briantist]

I was attempting to bootstrap a non-Ansible project, by copying my config from a collection and modifying a few things.
I forgot to add is_other_project and tried to generate the changelog, using:

antsibull-changelog release --version <ver> --date <date>

In this case it could not find galaxy.yml of course and it did warn about that, but it also completely ignored --version and used a version it discovered from ansible itself (the version of core, or in the case of 2.9, it used 2.9.27 or whatever it was). I think the date was correct.

The warning led me toward adding --is-collection to the command line which was confusing because I never had to do it before, thought it might have been new, but this was not the right direction for this situation (and it still ignored --version) :)

It took me quite a bit of time to figure out what was going on, I thought there might have been a bug with the new-ish functionality for automatically reading versions from python-based projects.

Of course it was my error, but I wonder if there might be a better way to catch or warn about this.

[felixfontein]

Actually, there's a bug, the warning/error should say --is-collection yes and not --is-collection no (for a collection without galaxy.yml). With --is-collection no, it basically assumes you are doing a release for ansible-core itself, and only accepts --version if also --codename is supplied.

In any case, it's somewhat hard to distinguish between a collection without galaxy.yml, and another project. In any case, it is probably a good idea to error out if it tries to do a ansible-core release where only one of --codename and --version is specified.

[felixfontein]

#105 should fix the things I commented on above.