Replies: 1 comment 1 reply
-
|
@stdedos I'm not sure GitHub even distinguished between But otherwise, not sure what you mean by "distancing ourselves" here? I had a quick re-read and one of them is a project setting (default branch) and the other is actual, existing branches, which I guess could lead to some discrepancies if GitLab allows setting these independently, but that is simply what the API returns. Is this an issue for python-gitlab specifically? |
Beta Was this translation helpful? Give feedback.
-
Oops 😅 I didn't notice that
Not so much, no (esp. after hearing the above) - but I did happened to get there, and I tend to interpret purple as "what the title says was a problem, and it was fixed and I don't need to really read it unless I'm really digging it".
That is exactly what I mean. If the API does that, then it does that. You are just an API wrapper. So "all these" are better expressed by the "Close as not planned. Won’t fix, can’t repro, duplicate, stale" state (i.e. Not planned) Either way, (again) thank you for taking the time @nejch 🙏 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I guess, since you are "distancing yourself" from the logic of Gitlab's output, you are not planning to "fix" this 😅
Beta Was this translation helpful? Give feedback.
All reactions