Jan Moringen

I made a branch which looks like it could work. You can try the binary from https://github.com/RDTK/generator/actions/runs/1416420320 (the other pipelines seem to be broken due to either end-of-life of the...

Is the prototypical implementation in the `wip-robocub` branch (binaries [here](https://jenkins-cse.bob.ci.cit-ec.net/job/build-generator-wip-robocup-ci-docker-build-generator-experiments/)) close to what you need?

> Is the prototypical implementation in the wip-robocub branch (binaries here) close to what you need? Sorry, I think I meant the `feature-auto-tagging` branch (binaries [here](https://jenkins-cse.bob.ci.cit-ec.net/job/build-generator-feature-auto-tagging-ci-docker-build-generator-experiments/)).

> The is no usage information in the feature-auto-tagging changelog. The job also does not show the changes. So i need some help how to use this branch. The changelog...

> Forgot token/user first which gave the same messages, but was able to look at the api endpoints from an incognito tab. Does missing access gives some different error? I...

> The include is still in the output file, should be removed after expanding. Should be fixed in [this build](https://jenkins-cse.bob.ci.cit-ec.net/job/build-generator-feature-auto-tagging-ci-docker-build-generator-experiments/48/). > I would also like if all "error" projects could...

> I personally would be fine with a simple #TODO after the commit: so i can grep the file for that but that does not sound like the cleanest solution....

I made a couple of additional changes. Please use the last successful build.

Did the most recent changes work OK for you?

> the header might contain sensible information like the key Can you provide more details? Passwords and API tokens should already be removed from the printed commandline. > commit entry...