 Hello, my name is William, and I wanted to talk today about how you can work on multiple merge requests using GitLab at the same time And so this is where today. I was just doing some work using both my local dev environment and GitLab's web IDE and I thought this is such a nice workflow. I love what's going on with the web IDE here I thought, hey, I'll just record a quick video to show all of you what I'm doing and how I use it And maybe somebody else can find it helpful as well So I'll just go ahead and share my screen for a moment and show you an MR that I am currently working on So here's a merge request to add Jenkins content to our comparison page and I have checked out this branch locally and And I have it here in my Adam editor where I've been doing some work by Updating features.yaml and this markdown file and this hamel file And so in these files, these are all related to this one MR where I'm essentially doing some work and doing an update and The use case here is I want one branch to do my development work But I also want to document the process that I'm going through So I created another merge request for the documentation Now I really really don't want this all in one merge request Because I don't necessarily want to block like I don't want to block on shipping the development work if the docs aren't done I want to be able to get it live and to iterate and for people to see and provide feedback So I really want these things to be separated so I can get individual feedback on each component You know, for example, if the instructions are clear what not So in this use case where you're doing one bit of development work on on one branch or one part recode base And then likely if you're then documenting what you're doing in the process for how to do that is in is in a separate place So here is my MR for the For the documentation changes and here I am using the web IDE So here's my other branch. So I'm essentially working on to get branches at the same time Almost and you know, you basically using two different editors and what's pretty cool about this is with the web IDE You could just open it in different tabs and work on multiple branches at the same time So here are my instructions for how to update The comparison page, you know, for example open this file and edit this So as I've been making changes here and Committing them to to this MR. I have also been simultaneously updating what I've been doing and documenting it In the GitLab handbook So I'll just finish this up the last thing I want to show is I have an example here of Adding a feature that GitLab has that a competitor or another tool does not have but I want to be sure to add an example of something that A competitor has for example Like puppet has a domain specific language For infrastructure configuration and that's something that is true for another tool But it's actually false for GitLab and so for us. It's important that our Comparisons are transparent and honest Just updates and formatting here add this one in like this and so Now I have the work that I've done in one branch and the documentation and the instructions in one branch and here I can commit locally and and push up on the one MR and here I can make commits in the you know added instructions on Features GitLab Does not have and I can commit to that branch. So I hope you all found this video fun entertaining just wanted to share with you how I use both my local dev environment and the GitLab web IDE to work on two Git branches at the same time that are Pushing changes to two different merge requests at the same time and I thought that was pretty fun So hope you all have a great day