amimas

> I would be happy to approve but I just have a little doubt about how will this handle versioning of gitlabform. > > The schema at https://raw.githubusercontent.com/gitlabform/gitlabform/main/schemas/gitlabform.json will -...

> Huh, any ideas why the acceptance tests fail with HTTP 401: > > ``` > E gitlabform.gitlab.core.UnexpectedResponseException: Request url='http://localhost/api/v4/groups/13/saml_group_links?per_page=100', method=GET, failed - expected code(s) [200, 404], got code 401...

@yantantether - Are you available to continue with this PR?

@yantantether - just checking if you're able to continue with this.

Hi @yantantether - no worries at all. Great that you're willing to continue with it. Thanks so much. A lot of updates took place lately. You'd want to update your...

Hi @admantium-sg - What else do you have in your gitlabform config under the `branches` section? I'm asking because looking at the log, it seems that where the error encountered....

> Is there a way to run gitlabform in debug mode and see the details of its requests to the GitLab API? You can run gitlabform with `--debug` option. It's...

> The only other change: on encountering the error, I update from gitlabform 3.6.0 to 3.7.0. I don't see any related changes in that version update that would've broken it....

> We want to apply the same ruleset to all projects. I think this goes back to the initial issue. Archived projects are read-only and your ruleset/config can change anytime...

I think I was wrong about how Gitlab treats archived projects. I did a quick test on a project using Gitlab's UI. The project was archived and I was able...