amimas
amimas
Should we close this and open individual issue if anything from this issue is still needed? It's labelled as feature request but original message is referring to multiple things and...
@ep-linden - to be clear, in that example, the effective config for `parent/subgroup` group setting does not configure additional settings mentioned in `parent` group config. Is that right?
I just realized that there is some collision between terms with the suggestion I posted above. For example, `project_settings` config key is associated with only part of the settings because...
I also need a "Total Coverage" for all projects but can't seem to get this to work. If I run `gradlew clean build`, I automatically get the coverage of each...
I believe the current syntax already allows using wild card pattern for branch names and set desired configs.
https://gitlabform.github.io/gitlabform/reference/protected_branches/
Yes, you're right. I was thinking of using global wildcard with just `*`. But this will make every single branches as protected. Yaml anchor is a good way to address...
> Or are you saying that would be done in GitLabForm's config (it's actually a project level setting but done at the group level)? Yes. That's what I meant. Creating...
I believe that's a default behaviour by Gitlab. It allows setting branch protection for a branch that doesn't exist yet. I agree the message in the UI maybe slightly misleading.
> I would have hoped that it only applied those settings to existing branches. This might be a separate feature request for gitlabform.