Greg Dubicki

> Curious what happens if it's set to `rootgroup/*` It doesn't work.: ``` >>> Getting requested groups or projects... Error: Project or group rootgroup/* cannot be found in GitLab! ```...

> Hello @gdubicki > back to my PC. > My configuration is like your third bullet point with target set to `rootgroup` - explaining the behavior I'm encountering. Thanks. I've...

The behaviour you observe is expected. If you have a group `gitlabform/*` and define `group_badges` for it then this is inherited by all the subgroups in this group. See https://gitlabform.github.io/gitlabform/reference/#configuration-hierarchy....

> > Is there a way to tell that I want the gitlab form configuration be only applied to this specific group (for instance "my_group/" instead of "my_group/*") and not...

Please check out an initial proposal for implementing this here https://github.com/gitlabform/gitlabform/wiki/Current-and-proposed-way-of-selecting-targets

Please use `--recurse-subgroups` flag for this, introduced in [v3.16.0](https://github.com/gitlabform/gitlabform/releases/tag/v3.16.0).

Sorry for a late reply. I obviously applaud the action upgrade but is token really a secret for public repos? I am sure that we made it plain text in...

> * https://gitlab.com/gitlabform is already claimed It's mine so we can use it if we want to. ☺️

> So far the main blocker on the CI front is getting the acceptance tests to run with how GitLab handles Docker commands on it's runners We should check how...

> publishing to GitLab not GitHub Pages This is great, we will switch to those with a redirect from the old address. > …and Container Reg I would switch back...