amimas

@hertzsprung - any update available from you on this? I was able to reproduce this in PR #857 when added new acceptance tests. Please see the description of that PR....

@hertzsprung - The PR mentioned above has been merged and released in v4.0.1. It should be resolved now. Closing this as fixed.

Thanks for the suggestion @nickgriffiths. What should the gitlabform config syntax look like? Can you post some proposals? Will you or any of your colleague be able to contribute this...

Sounds good. Thanks @nickgriffiths

Hi @TimKnight-DWP - Thank you for wanting to contribute this feature. Really appreciate the help. In terms of config syntax, here's what I'm thinking, although it's not too different from...

> Under job_token_scope, I added an attribute named enabled. This doesn't have to be part of this issue's implementation, but I'm including it for the sake of completeness because it's...

Thanks @TimKnight-DWP. Forgot that the boolean option is deprecated and expected to be removed in v17. As for a group being added to the allowlist, your first suggestion makes sense...

Hi @TimKnight-DWP . I'm not well versed in python packaging yet. I think you need to update the version reference in setup.py here: https://github.com/gitlabform/gitlabform/blob/dd58a7a2df60a1a5b8fe6a9cdf127ae1bf79ee5a/setup.py#L55 According to this article you can...

I was looking at that setting in a project for work today. There're 2 settings. One is called "limit access to this project". The 2nd one is called "limit access...

Thanks for digging into that boolean setting. Hopefully things get clarified. > Let's call the first boolean `limit_access_to_this_project` ? bit wordy but does map to Gitlab? > Maybe GLF should...