Submit an assignment as a merge request

When you have fulfilled all the requirements, it's time to hand in using the GitLab feature merge request.

0. Preparation

Before you begin this guide, please make sure that you fulfill these requirements:

  1. All mandatory requirements (functional and non-functional) of the assignment are fulfilled.

  2. The latest codebase is in the main branch of your project and pushed to GitLab. The correct output for running git status would be:

    ‌‌‌‌‌

1. Create a new merge request

Create a new merge request by following these steps on GitLab:

  1. Navigate to the repository of your completed assignment.
  2. Click on "Merge request" in the left navigation menu.
  3. Select "New merge request".
  4. Select "main" as the source branch, and "lnu/submit" as the target branch.
  5. Click "Compare branches and continue".

2. Fill in the form "New merge request"

Fill in the form as:

  1. Title: SUBMIT: Assignment {ASSIGNMENT NUMBER} where {ASSIGNMENT NUMBER} is replaced with the number of the assignment. Example: SUBMIT: Assignment 3.
  2. Fill in the submit report by adding "x" to the checkboxes according to the example "I have started working on the assignment.".
  3. At the end (Assignment report), you may give specific feedback to the course management about the assignment. Make sure to read the instructions. In some assignments, you might need to take further actions or write an extended assignment report.
  4. Assignee: Leave as Unassigned.
  5. Milestone: Here, you need to choose which Milestone (examination occasion) you are submitting your code to. Pay attention to choosing the correct one in the list (match assignment number and date).
  6. Labels: Select Submitted.
  7. Merge request dependencies: leave as is.
  8. Approval rules: leave as is.
  9. Merge options: leave as is.

3. Submit

Submit your assignment by clicking "Create merge request".

Now the following will happen:

  1. A new merge request pipeline will start executing. This pipeline may do things like testing and linting your code. Or it may not. This depends on the setup of the assignment.
  2. The pipeline will also test if the assignment was submitted before the deadline. If not, the examiner may fail your submission.

📢 When you have submitted your assignment, please do not close the merge request. If you do, that will count as if you have canceled the submission

4. Bugfixes after submission

It is not unusual to find bugs in your code after the submission. You can alter your code even after submission by committing and pushing to the main branch as usual. Note that committing after the deadline will make your submission tagged as a late submission in the pipeline. Please avoid this if possible.

5. Canceling the submission

If you want to cancel your submission, you can do that by clicking "close merge request" on the summary page of the merge request. Closed merge requests will not be assessed.