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
b3da5e15
Commit
b3da5e15
authored
May 16, 2017
by
Luke "Jared" Bennett
Committed by
Rémy Coutable
May 16, 2017
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update ee_compat_check.rb to include `git apply --reject` suggestion
parent
c6fd3b6a
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
0 deletions
+11
-0
lib/gitlab/ee_compat_check.rb
lib/gitlab/ee_compat_check.rb
+11
-0
No files found.
lib/gitlab/ee_compat_check.rb
View file @
b3da5e15
...
@@ -310,6 +310,17 @@ module Gitlab
...
@@ -310,6 +310,17 @@ module Gitlab
Resolve them, stage the changes and commit them.
Resolve them, stage the changes and commit them.
If the patch couldn't be applied cleanly, use the following command:
# In the EE repo
$ git apply --reject path/to/
#{
ce_branch
}
.patch
This option makes git apply the parts of the patch that are applicable,
and leave the rejected hunks in corresponding `.rej` files.
You can then resolve the conflicts highlighted in `.rej` by
manually applying the correct diff from the `.rej` file to the file with conflicts.
When finished, you can delete the `.rej` files and commit your changes.
⚠️ Don't forget to push your branch to gitlab-ee:
⚠️ Don't forget to push your branch to gitlab-ee:
# In the EE repo
# In the EE repo
...
...
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