Change the approach to check if patches apply cleanly
What does this MR do?
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
CHANGELOG entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master
(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Closes #23372 (closed)
Merge request reports
Activity
- Resolved by Robert Speicher
Mentioned in issue #23371 (closed)
Mentioned in issue #23568 (closed)
Added 494 commits:
-
a09fefd4...6ff3625f - 493 commits from branch
master
- b433422e - Change the approach to check if patches apply cleanly
-
a09fefd4...6ff3625f - 493 commits from branch
Added 1 commit:
- 12115682 - Change the approach to check if patches apply cleanly
@rspeicher I think this is now in a working state, I've simplified and solidified the task a bit. Let me know what you think!
Milestone changed to %8.14
Reassigned to @rspeicher
Added 1 commit:
- af669cbe - Change the approach to check if patches apply cleanly
- Resolved by Rémy Coutable
- Resolved by Robert Speicher
- Resolved by Rémy Coutable
@rymai Sorry, one more nitpick!
Reassigned to @rymai
Added 1 commit:
- 402dcab4 - Use File.write instead of File.open + File#write
Enabled an automatic merge when the build for 402dcab4 succeeds
@rymai LGTM!
Do we have docs for this yet, or are we waiting until it's working as expected?Mentioned in issue #23740 (closed)
@rspeicher Thanks! Hmm, no there's no doc for this yet. But I will definitely add this under https://docs.gitlab.com/ce/development/README.html. Created an issue via our awesome Issue Board feature! :)
Reassigned to @rspeicher
@rymai RuboCop failures. We might want to encapsulate the output to a single helper method that calls
puts
and then we can wrap it in arubocop:disable ... rubocop:enable
block comment.Reassigned to @rymai
Added 1 commit:
- d38d4a9e - Disable Rails/Output cop since it makes no sense here
@rspeicher I've disabled the cop entirely (d38d4a9e) since it makes no sense to have it in this case, ok for you?
Reassigned to @rspeicher
@rymai Works for me!
Mentioned in commit nvan/gitlab-ce@ea8aa34b
This MR was in a locked state. I used the console to manually unlock it (
.unlock_mr!
) and then mark it as merged (.mark_as_merged!
).See https://gitlab.com/gitlab-org/gitlab-ce/commit/ea8aa34b55f9029a823c6210258f8552fcaababe