How to raise pr from GitLab?
In GitLab, raising a Pull Request (PR) is equivalent to creating a Merge Request (MR). It allows you to propose changes to a repository and request their review and integration into the main branch. Here's a step-by-step guide to raising a Merge Request in GitLab:
1. Fork or clone the repository
- If you're working on a shared repository, clone it using:
git clone <repository_url> - If you're contributing to someone else's project, fork the repository and clone your fork.
2. Create a new branch
- Always work on a new branch to keep your changes organized.
- Create and switch to a new branch using:
git checkout -b <branch_name>
3. Make your changes
- Edit the code, add files, or modify existing ones.
- Use Git to track your changes:
git add . git commit -m "Description of changes"
4. Push your branch
- Push the new branch to the remote repository:
git push origin <branch_name>
5. Create a Merge Request (MR)
- Navigate to the GitLab repository in your browser.
- Go to the Merge Requests tab in the left-hand menu.
- Click New Merge Request.
- Select the source branch (your feature branch) and the target branch (usually
mainormaster). - Click Compare branches and continue.
6. Fill in the Merge Request details
- Title: Provide a concise title for your changes.
- Description: Explain what changes you've made and why.
- Assign reviewers: If required, assign teammates or maintainers to review your MR.
- Labels: Add any relevant labels (e.g.,
bug,enhancement). - Click Create Merge Request.
7. Respond to feedback
- Reviewers may leave comments or suggest changes. Make the required updates in your branch and push the changes.
- Once changes are pushed, GitLab will automatically update the Merge Request.
8. Merge your changes
- If you have the necessary permissions and the MR is approved, merge it using the Merge button. Otherwise, the repository maintainer will handle the merge.
Tips
- Ensure your code follows the repository's contribution guidelines.
- Regularly pull changes from the target branch to avoid merge conflicts:
git pull origin <target_branch>
By following these steps, you can successfully raise a Merge Request in GitLab, collaborate with your team, and get your changes integrated into the project.
TAGS
Coding Interview
System Design Interview
CONTRIBUTOR
Design Gurus Team
-
GET YOUR FREE
Coding Questions Catalog
Boost your coding skills with our essential coding questions catalog.
Take a step towards a better tech career now!
Explore Answers
How do I get good at software interviews?
How do you execute cross‑shard joins/aggregations efficiently?
Learn how to execute cross shard joins and aggregations efficiently in distributed databases. Explore proven patterns like local, broadcast, shuffle, and semi joins, plus best practices for minimizing data movement, handling skew, and improving performance across shards.
Which tool is used for ReactJS?
How do you win coding challenges?
How much does Twilio pay per call?
What is the DP problem?
Related Courses
Grokking the Coding Interview: Patterns for Coding Questions
Grokking the Coding Interview Patterns in Java, Python, JS, C++, C#, and Go. The most comprehensive course with 476 Lessons.
4.6
$197

Grokking Modern AI Fundamentals
Master the fundamentals of AI today to lead the tech revolution of tomorrow.
3.9
$78
Grokking Data Structures & Algorithms for Coding Interviews
Unlock Coding Interview Success: Dive Deep into Data Structures and Algorithms.
4
$78
One-Stop Portal For Tech Interviews.
Copyright © 2025 Design Gurus, LLC. All rights reserved.