I recently discovered that GitLab (with some additional settings) can provide a “Rebase” button, displayed on merge requests if the source branch is behind target branch in terms of commits
This thing is mainly useful because it eliminates the need to use the command line for this action, making the workflow more accessible to users who may not be comfortable with CLI or Git’s more advanced features.
It’s also definitely an improvement to the developer experience by reducing friction during the merge request process. Whether you’re an experienced developer or just getting started with Git, this feature makes it easier to keep branches up-to-date and maintain a clean commit history without switching tools. While it’s not a silver bullet—conflicts still need to be handled manually—this feature enhances productivity and simplifies workflows in a way that many teams will appreciate.
Steps to enable this feature
1. Go to the project’s Settings > Merge requests
2. Change the default merge method with one of the following
3. Save the changes
Conclusion
- The ‘Rebase’ button in GitLab helps keep branches up-to-date and simplifies the rebasing process.
- It’s a powerful tool to maintain clean, linear Git history, avoiding merge commits.
- The button is available directly in the merge request UI, minimizing the need for command-line Git operations.
Enjoyed this article? Make sure to subscribe to my YouTube Channel for more Test Automation tutorials, and follow me on LinkedIn and Twitter for regular insights.
Looking to improve your test automation skills?
I’ve created a personalized 1-on-1 Mentoring program refined to boost YOUR CURRENT skills. Reach out at iamrv@razvanvancea.ro for more details and together will create a learning path adapted to your skills and goals that you are aiming for, in a timely-efficient manner🚀