Commit graph

10 commits

Author SHA1 Message Date
GitLab Bot
fcda041fc0 Add latest changes from gitlab-org/gitlab@master 2020-07-09 12:08:56 +00:00
GitLab Bot
e2d4a6dedb Add latest changes from gitlab-org/gitlab@master 2020-05-14 00:07:47 +00:00
GitLab Bot
c7ba7b9976 Add latest changes from gitlab-org/gitlab@master 2020-05-11 09:09:45 +00:00
GitLab Bot
c6a33b2982 Add latest changes from gitlab-org/gitlab@master 2020-04-10 12:09:36 +00:00
GitLab Bot
b3a736ed88 Add latest changes from gitlab-org/gitlab@master 2020-02-14 15:09:08 +00:00
GitLab Bot
22e9af3c8b Add latest changes from gitlab-org/gitlab@master 2020-01-27 12:08:35 +00:00
GitLab Bot
7480d774df Add latest changes from gitlab-org/gitlab@master 2019-12-17 00:07:59 +00:00
GitLab Bot
00bfd2d81d Add latest changes from gitlab-org/gitlab@master 2019-11-16 21:06:10 +00:00
Paul Slaughter
d4cc92db09
FE remove create branch call in IDE commit
Previously `start_sha` was intercepted on the frontend to create the
correct branch in a separate API call. Now that the commits API supports
the `start_sha` parameter directly this workaround is not needed
anymore.
2019-07-18 09:19:18 +02:00
Paul Slaughter
894ad6f6e9
Fix IDE commit to use start_ref
**Why?**
The branch HEAD could be changed since the
IDE was opened. This leads to user's unintentionally
creating commits that overwrite other changes.

https://gitlab.com/gitlab-org/gitlab-ce/issues/59023
2019-06-17 14:04:35 -05:00