amimas

Hey @adam-moss - Shouldn't this be supported already since the `member_role_id` is just another attribute of [group/project members API](https://docs.gitlab.com/ee/api/members.html#edit-a-member-of-a-group-or-project). I didn't check the code yet. Since gitlabform follows the raw...

@adam-moss - did you get a chance to try it out yet?

Thank you for verifying. I just took a quick peak at the code for project membership. Looks like "all the data" from the config is not being passed to the...

In my opinion, it makes sense that this is available via python-gitlab library. There's an open issue about it too https://github.com/python-gitlab/python-gitlab/issues/1357 Of course I can't speak for that library. Hopefully...

Have you used [renovate](https://docs.renovatebot.com/)? I'm not familiar enough with dependabot. So, can't say if renovate would be more useful instead. Thought I'd mention it in case it's something worth trying...

I suggest we keep this open. Even when we move to gitlab.com, this will still need to be worked on.

I like the concept or idea of type checking and validation. But, I'm really new to Python and don't have enough experience to suggest whether to keep using `mypy` for...

Thanks for the idea @glensc . I think it should probably be another top-level key under a project similar to `branches`, `deploy_keys`, `hooks`, etc. Can you suggest a full config...

Thanks for all that details @glensc . I haven't used GitLab's "Feature flags" yet, but here's my thought. I like your config syntax suggestion. One minor tweak I would propose...

Hi @kriko - Thanks for opening the issue. > GitLabForm has a feature to apply settings from a parent group to sub-groups, however this can lead to unexpected configuration that...