Timo Furrer

Implementing in go-gitlab pending to be merged and released: * https://github.com/xanzy/go-gitlab/pull/1403

@teekhandekar there is already ongoing work for that in https://github.com/gitlabhq/terraform-provider-gitlab/pull/926 (btw. you can check that in the `Development` section to the right of the issue description ;)). The problem at...

Thanks for the report @igorbrites 👍 I've managed to reproduce this using the following minimal terraform config: ```hcl resource "gitlab_project" "default" { name = "issue-1119" import_url = "https://github.com/timofurrer/test.git" mirror =...

btw. I've created an upstream issue in the meantime to get some help for this: https://gitlab.com/gitlab-org/gitlab/-/issues/364392

@teekhandekar Yes, feel free to open a PR for that. @armsnyder has pretty much laid out the implementation steps already. In addition, can you implement all the *shared runners* fields....

Thanks for open this @genei09 The reason for this behavior is that the upstream GitLab API doesn't return the `ref` the user provided when the branch was created. Therefore, when...

@genei09 Yes, I agree. > So other than being necessary for create, it's not really helpful in the ongoing management. The branches will naturally diverge and the origination of the...

The problem here is that the `gitlab_deploy_key_enable` resource explicitly deletes the Deploy Key during the `destroy` 🤷 (not sure if that was by intention, ...) However, there isn't a disable...

@Shocktrooper Yes, if it's not already in go-gitlab - it needs to support it first. We've decided to exclusively use go-gitlab :)

> Going forward we should just turn on the feature flag in the startup script and just test this without sentry and only use the integrated backend. Yes, I agree....