Timo Furrer

@hulquest Yes, I think it indeed is. Do you mind opening an issue upstream and I'll close this one? In case there would be any news - we can always...

@hulquest thanks for the update though!

I've made a proposal for how to support this with very low effort and I'm describing the current issue in the PR in case anyone is interested in a discussion:...

@PatrickRice-KSC the suppress diff func would be a neat solution probably - BUT you won't have access to the GitLab client from `meta` like you do in the crud functions...

@nagyv @armsnyder as a first step and to kinda lay out a roadmap, what would you think is the best way to just "measure" the coverage for now? It doesn't...

@armsnyder sounds like a fun and valuable little project, thus go ahead 🍰 @nagyv yes, I was talking about the REST API only for now. To be honest, I haven't...

> Hey @timofurrer - I wonder if we could apply the same workaround for go-gitlab here that we did over here: [#971 (comment)](https://github.com/gitlabhq/terraform-provider-gitlab/pull/971#discussion_r835801777) @PatrickRice-KSC hmmm, where would you see the...

@Moon1706 thanks for the detailed questions and the links, super helpful! I suggest to do the following: * Implement the `Milestones` field in the go-gitlab API. * as documented with...

@Shocktrooper Are you also testing against a 14.9 GitLab instance? The reason why the code you've referred above even exists was because `default_branch` wasn't properly supported in the API. However,...

@Shocktrooper okay, interesting, can you work out a minimal reproducible example?