-
Notifications
You must be signed in to change notification settings - Fork 645
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gitlab server should handle the draft status #1160
Comments
first share more details. |
I never said that something is not working today. It is a proposal to handle the "draft" status. |
i approved the PR. Notice that this is not "gitlab webhook server", and that's what led to my pondering. |
@mrT23, thanks, but the pull request was unrelated to this issue; I just faced that bug today while trying to integrate it into a gitlab pipeline. To add some useful info here, at the moment, AFAIK, the Gitlab Server handles two statuses: I was suggesting that draft merge requests could be excluded from merge request parsing using a configuration toggle. It should be easy to implement and offer several advantages. On the one hand, it reduces the traffic to the selected AI vendor for unwanted parsing, and on the other hand, it respects the draft semantics. |
welcome to open a PR also for this |
Thanks @mrT23 |
This is an enhancement propsal.
I think that would be useful if the gitlab webhook server could be capable to discard MR in draft status, of course this should be a configurable behavior.
If you think this is useful, I can try to implement it.
The text was updated successfully, but these errors were encountered: