Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
2257fda3
Commit
2257fda3
authored
Aug 17, 2016
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Reference the version 'UI resolve conflicts' was introduced
[ci skip]
parent
7cb76ce1
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
0 deletions
+4
-0
doc/user/project/merge_requests/resolve_conflicts.md
doc/user/project/merge_requests/resolve_conflicts.md
+4
-0
No files found.
doc/user/project/merge_requests/resolve_conflicts.md
View file @
2257fda3
# Merge conflict resolution
# Merge conflict resolution
> [Introduced][ce-5479] in GitLab 8.11.
When a merge request has conflicts, GitLab may provide the option to resolve
When a merge request has conflicts, GitLab may provide the option to resolve
those conflicts in the GitLab UI. (See
those conflicts in the GitLab UI. (See
[
conflicts available for resolution
](
#conflicts-available-for-resolution
)
for
[
conflicts available for resolution
](
#conflicts-available-for-resolution
)
for
...
@@ -35,3 +37,5 @@ Additionally, GitLab does not detect conflicts in renames away from a path. For
...
@@ -35,3 +37,5 @@ Additionally, GitLab does not detect conflicts in renames away from a path. For
example, this will not create a conflict: on branch
`a`
, doing
`git mv file1
example, this will not create a conflict: on branch
`a`
, doing
`git mv file1
file2`
; on branch
`b`
, doing
`git mv file1 file3`
. Instead, both files will be
file2`
; on branch
`b`
, doing
`git mv file1 file3`
. Instead, both files will be
present in the branch after the merge request is merged.
present in the branch after the merge request is merged.
[
ce-5479
]:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5479
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment