summaryrefslogtreecommitdiff
path: root/changelogs/unreleased/only-create-unmergeable-todo-once.yml
diff options
context:
space:
mode:
authorSean McGivern <sean@gitlab.com>2017-02-24 15:56:41 +0000
committerSean McGivern <sean@gitlab.com>2017-02-24 17:18:12 +0000
commit2da8bc3de9f8b63bd80a081c7e2880adee3edb71 (patch)
treebab714b283a3690d03301241663bebcb41509e40 /changelogs/unreleased/only-create-unmergeable-todo-once.yml
parentfc567da473072bf11ea8d0fe8ddf9a596349f03f (diff)
downloadgitlab-ce-2da8bc3de9f8b63bd80a081c7e2880adee3edb71.tar.gz
Only create unmergeable todos onceonly-create-unmergeable-todo-once
Previously, we created an unmergeable todo when a merge request: 1. Had merge when pipeline succeeds set. 2. Became unmergeable. However, when merge when pipeline succeeds fails due to unmergeability, the flag isn't actually removed. And a merge request can become unmergeable multiple times, as every time the target branch is updated we need to re-check the mergeable status. This means that if the todo was marked done, and the MR was checked again, a new todo would be created for the same event. Instead of checking this, we should create the todo from the service responsible for merging when the pipeline succeeds. That way the todo is guaranteed to only be created when we care about it.
Diffstat (limited to 'changelogs/unreleased/only-create-unmergeable-todo-once.yml')
-rw-r--r--changelogs/unreleased/only-create-unmergeable-todo-once.yml4
1 files changed, 4 insertions, 0 deletions
diff --git a/changelogs/unreleased/only-create-unmergeable-todo-once.yml b/changelogs/unreleased/only-create-unmergeable-todo-once.yml
new file mode 100644
index 00000000000..e675ed945ad
--- /dev/null
+++ b/changelogs/unreleased/only-create-unmergeable-todo-once.yml
@@ -0,0 +1,4 @@
+---
+title: Only create unmergeable todos once when MR fails to merge
+merge_request:
+author: