Challenge Overview
Challenge Overview
A large company wants to drive some changes to the Gitlab CE source code to allow Post Review functionalities. It’s asking Topcoder to work with Gitlab engineers to get that working.
��� The basic goal of the challenge
The goal of the challenge is to start the development of the fix for the Gitlab issue below:
https://gitlab.com/gitlab-org/gitlab-ce/issues/62817
��� Technology and Framework details
- Ruby (MRI) 2.6.3
- Git 2.8.4+
- Javascript
- Redis 2.8+
- PostgreSQL (preferred) or MySQL
Project Background
��� The client wants to be able to do Post Review using the Gitlab CE application:
��� An issue and an Epic have been created in Gitlab with the functionalities details. Check them here:
Requirements
��� Setup Gitlab CE development using the development Kit. Create a bash shell script to automate the process. It must run on both Linux or Mac OS:
��� Add new models / controllers (API) / tables to handle adding commits to an existing Merge Request (for additional details check Gitlab issue. Any doubts post in the forum):
-
Create model MergeRequestContextCommit and MergeRequestContextCommitDiffFile
-
Add table merge_request_context_commits and merge_request_context_commits_diff
-
Use MergeRequestDiffCommit and MergeRequestDiffFile as starting point
��� Modify the MergeRequestController to allow adding new MergeRequestContextCommit and MergeRequestContextCommitDiffFile to the MR.
��� Only backend should be changed at the moment. Therefore, you must provide a way to validate the submission. The validation should cover:
-
Create a Merge Request
-
Add existing commits to the MR for Post Review
-
Show diff from these added commits along with the MR commits against the target branch
Final Submission Guidelines
- Patch against the Gitlab CE source code