Maybe, just maybe, this thing can be supported by CLI or by Github Actions
I never tested, but if this staff works, CLI is the place where it can work. With default integration like Github or BitBucked it, most likely, will not work, because of connector strict logic.
Why you need them? Just curious. If you have a good workflow idea, maybe it’s better to ask for a feature request? Please describe step by step what you need to achieve, probably using out-of-box tools would be even faster to see the final result.
But @tbsprs if you decide to switch to CLI, keep in mind that some time ago I was told in private conversation that it’s better to have a configuration for lang mapping in the project itself, because this CLI mapping may soon disappear and remain in project only. I have no timeline, maybe it’s even 3+ years, still…
I agree that configuration-as-code makes very much sense. No doubt here.
Regarding the usage of the web interface and CLI I would appreciate if you can make it very clear in the documentation if there are differences in the supported features. For now, I only saw project id and API token being required for CLI (alternatively they can be passed as shell parameters).