- 01 Aug, 2017 1 commit
-
-
Gabriel Mazetto authored
-
- 13 Jul, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 29 Jun, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 02 Mar, 2017 1 commit
-
-
Douwe Maan authored
-
- 01 Mar, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 26 Jan, 2017 2 commits
- 06 Jan, 2017 2 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 04 Jan, 2017 5 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
We merge repository checks inside it so we don't have to check it on the call site, and we could also load the commit for the caller. This greatly reduce code duplication. Feedback: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7237#note_20572919
-
Lin Jen-Shin authored
-
- 13 Dec, 2016 4 commits
-
-
Lin Jen-Shin authored
if it happens. Feedback: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7237#note_19747933
-
- 09 Dec, 2016 1 commit
-
-
Lin Jen-Shin authored
-
- 08 Dec, 2016 3 commits
-
-
Lin Jen-Shin authored
commits from the other repository. We'll cleanup the tmp ref after we're done with our business.
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
more consistent across different methodst
-
- 07 Dec, 2016 2 commits
-
-
Lin Jen-Shin authored
So we still commit outside the hooks, and only update ref inside the hooks. There are only two exceptions: * Whenever it's adding a tag. We can't add a tag without committing, unfortunately. See !7700 * Whenever source project is in another repository. We'll need to fetch ref otherwise commits can't be made. See the whole discussion starting from: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7237#note_19210942
-
- 06 Dec, 2016 1 commit
-
-
Lin Jen-Shin authored
Add back check if we're losing commits in a merge.
-
- 05 Dec, 2016 1 commit
-
-
Lin Jen-Shin authored
git operation inside GitHooksService. Feedback: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7237#note_19210942 TODO: Fix tests for update_branch_with_hooks
-