Skip to content
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

Fix unassign when author is marge #211

Merged
merged 1 commit into from
Jun 21, 2019
Merged

Fix unassign when author is marge #211

merged 1 commit into from
Jun 21, 2019

Conversation

JaimeLennox
Copy link
Contributor

According to the docs:

"Set to 0 or provide an empty value to unassign all assignees."[1]

So setting to None seems like it would work, although in practice it doesn't.

I've manually tested with 0 and it works fine.

[1] https://docs.gitlab.com/ee/api/merge_requests.html#update-mr

Fixes: #189

According to the docs:

"Set to 0 or provide an empty value to unassign all assignees."[1]

So setting to `None` seems like it would work, although in practice it
doesn't.

I've manually tested with `0` and it works fine.

[1] https://docs.gitlab.com/ee/api/merge_requests.html#update-mr
@JaimeLennox JaimeLennox requested a review from aschmolck June 15, 2019 19:18
@micheelengronne
Copy link

The problem is that it remove the PR from any assignee. Making it lost in the void :)

@micheelengronne
Copy link

I am working on a solution to avoid the flood that keeps assignees #210 I just have to figure out how to add an endpoint in the mock.

@aschmolck aschmolck merged commit d8e0b15 into master Jun 21, 2019
@aschmolck
Copy link
Contributor

@micheelengronne Removing the PR from any assignee (and maybe leaving a comment about user error) is the correct behaviour. Marge-bot is not meant to be the author of PRs, and although this should fail gracefully (maybe with an explanatory note), I'm not interested in code support beyond this, since it's nothing that can ever work particularly well in the first place.

Having said that, if there is something that would be desirable for other reasons and helps this unsupported use case I might still consider merging it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Maximum number of reassigns
3 participants