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
0
Merge Requests
0
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
Boxiang Sun
gitlab-ce
Commits
a9a58156
Commit
a9a58156
authored
Mar 03, 2017
by
Sean McGivern
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'ee-comp-mr-2' into 'master'
Improve EE compatibility MR docs [ci skip] See merge request !9681
parents
4f44717d
b566336b
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
1 deletion
+4
-1
doc/development/limit_ee_conflicts.md
doc/development/limit_ee_conflicts.md
+4
-1
No files found.
doc/development/limit_ee_conflicts.md
View file @
a9a58156
...
@@ -53,9 +53,12 @@ Notes:
...
@@ -53,9 +53,12 @@ Notes:
-
Code reviews for merge requests often consist of multiple iterations of
-
Code reviews for merge requests often consist of multiple iterations of
feedback and fixes. There is no need to update your EE MR after each
feedback and fixes. There is no need to update your EE MR after each
iteration. Instead, create an EE MR as soon as you see the
iteration. Instead, create an EE MR as soon as you see the
`rake ee_compat_check`
job failing and update it after the CE MR is merged.
`rake ee_compat_check`
job failing. After you receive the final acceptance
from a Maintainer (but before the CE MR is merged) update the EE MR.
This helps to identify significant conflicts sooner, but also reduces the
This helps to identify significant conflicts sooner, but also reduces the
number of times you have to resolve conflicts.
number of times you have to resolve conflicts.
-
You can use
[
`git rerere`
](
https://git-scm.com/blog/2010/03/08/rerere.html
)
to avoid resolving the same conflicts multiple times.
## Possible type of conflicts
## Possible type of conflicts
...
...
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