Submitting Your Course

After previewing and testing your course locally, the final step is to submit it for review. This is done via a GitLab merge request. In this lesson, we will go over the process of preparing and submitting your course.

Preparing Your Course for Submission

Before submitting, ensure that:

1. All your course content is complete and thoroughly tested
2. Your course follows the structure and guidelines described in the previous lessons
3. All media files (images, videos) are correctly placed and referenced
4. Your course metadata (in the front matter of your files) is accurate and complete

Creating a Merge Request

Follow these steps to create a merge request for your course:

1. Commit your changes: Open your terminal and run:

   git add .
   git commit -m "Added new course: <Your Course Name>"
   

2. Push your branch: If you haven’t already, push your branch to the remote repository:

   git push origin courses/<your-course-name>
   

3. Create the merge request:

   • Open your web browser and go to the GitLab repository
   • Click “Create Merge Request” (you may see this option after pushing your branch)
   • If not, navigate to the “Merge Requests” section and click “New Merge Request”

4. Fill out the merge request:

   • Set the source branch to your course branch
   • Set the target branch to main
   • Give your merge request a title, e.g., “New Course: Introduction to Git”
   • Provide a brief overview of your course and any relevant information for the reviewers in the description

5. Submit the merge request:

   • Review all your changes one last time
   • Click “Submit Merge Request”

The Review Process

After submitting your merge request:

1. Reviewers will examine your course content, structure, and adherence to guidelines
2. You may receive feedback or requests for changes
3. Be ready to make revisions based on the feedback
4. Once approved, your course will be merged into the main branch and published on the platform

Best Practices for Merge Requests

• Be responsive: Regularly check your merge request for comments or feedback
• Be open to feedback: The review process ensures high-quality content. Be open to suggestions for improvement
• Test after changes: If you make changes based on feedback, always test your course locally before pushing updates

Exercise: Submit Your Course

1. Review your entire course one last time
2. Commit all your changes and push your branch
3. Create a merge request following the steps outlined above
4. Write a brief overview of your course and what learners can expect in the merge request description

Congratulations! You have now completed the entire process of creating and submitting a course for git.nrw. In our final lesson, we will summarize what we’ve learned and discuss next steps for course creators.