 publish it. But what did you think about the common P suggestion, Barbie? So I think the common command P recommendation will save me a lot of time in trying to have to scroll through the sidebar here in the project to find exactly where I want to make a change. So I am thrilled to know I can press command P and then use the words and a space to find where I need to go. I think it's key to know though that it's not a slash so you don't copy exactly like it is in the URL. And instead of a slash, you use a space. And I think that's a key thing that people could get wrong if they're not used to working in. Adam. Cool. So I'm going to scroll down to chat. Did I always go past it? I'm going to give you some time. I'm going to give a bit of an introduction about that common P thing that we talked about. The common P thing was like, okay, I want to make a change on the website. And I know that I'm looking on like the communication page of the handbook, the URL slash handbook slash communication. How do I find that in the editor? And the way to do it is you can navigate the left hand menu, but it's quicker to press command P and type some words that are in the URL that are unique and then have space between them and type them in the order you want to see that mostly tends to find the thing straight away. Okay, so I have not yet switched my master here. So usually I would go into tower and I know said you don't usually use tower. And I was introduced to it by Eric and I thought it made things easier. So I go down to master, I right click, I choose my branch, I usually name it by my initials first, which now are BJB. And then I would go here and say, chat, I'm wanting to make an update update about when people are out of the office. So I might just say oh, oh, may I recommend you not name it with something that that that is your personal thing that the thing you want to avoid is your personal workspace. And this kind of feels like it. This is my thing. And for example, is suppose I see your branch and I notice you have a big spelling mistake that I can leave a comment. But what you really want is people to push on your branch and fix the spelling mistake much easier. They don't have to say we're free out of but by you're courting it off, you're saying it's mine. It's not like it's not sit lap, it's get lab. It's not it shouldn't be it shouldn't be about you, it should be about the change you want to make. Okay, so when I started, I was given the guidance to do that so that there wasn't naming convention issues and it helped make sure that the chances that someone else will push the same branch are very low because just give it the name of the change you want to see. So you want to see chat out of office great. I think the chances of someone doing this in the time it takes to turn around this metro question, which should be like 24 hours or something like that are very low. And if it if that's the case, they just rename it. But I don't think it happened in the history of the company. Okay, so here's another question I have, because I was also trained to train to do three, not just two, I could leave it just like this with this too. Yeah, to it's to it's fine, considering considering our volume. Now the thing you would if there's an issue that this relates to that is on the WWW get lab issue tracker, you can start with that number that will automatically close the issue when this gets merged. So that might be an interesting thing. But okay, this case, I understand there's no issue. There I don't think there is. And that's great to know. So I start with the issue number. Do I have to do the hashtag sign first? No, that's just the issue number and then a hyphen. Okay, just the issue number and the hyphen and automatic connect. That's awesome. You've got some great stuff here. Okay. So then I do that. And then that automatically usually automatically changes it here in Adam as well to show that same branch. And then I'm going to come over here. And the reason I'm doing this update today is because I've experienced and I've gotten feedback from other get labbers that when people are out of the office and they're getting mentioned in chat rooms in Slack, and they're not checking Slack every day and they shouldn't they're on vacation. Then when they come back, it's really hard for them to find all their different mentions there. So I wanted to do a chat update here in the handbook just to recommend that if you know that someone's on vacation, either because you looked at, you know, from their calendar, you know, because you've spoken to them, or ideally they say in Slack that they're on vacation and they put themselves out of office in Slack, then avoid mentioning them in Slack because it may be hard for them to go back and find those if you do mention them, then you might want to check back when they get back from vacation. So I wanted to do something there for updating that in the handbook. So let me take a moment to write that up. Is Slack rooms the right, how would I phrase that? I would say in a high volume channel. Like if it's, if it's our pricing channel or handbook channel doesn't matter, if you're mentioning someone in development or general than that or random, high volume chat channel, you can make it using an email maybe better or just leave it at that. Yeah, it depends a bit like, you know, had these, these conference, you want to mention them because there's a relevant conversation going on. So how are you going to point them to them? So there's an email, what are you going to put in the email? I think directly, you're in Slack already. So now they're not, they're not finding out about this thing that's super relevant to them. And they're not going to, they're not going to know anyway. So I would say leave just send them personally a link to that message. Although I noticed that Slack links are a bit broken, but I think so be it. We can't help that. Hopefully Slack will fix it at some point. So I would say, send them the URL that links to the message in a direct message on chat. Okay, even though you don't URLs are good, you still would recommend sending the URL? Yeah, I think it's the best option. And I hope that's like, we'll fix this soon, because the problem is what what it will show Slack will just show you, you've been mentioned, and there's been 3000 common sins, like, yes, thank you very much, Slack, you can use common find. So it's super hard. But if if it's like, a link to the relevant Slack message, then it will just scroll to there. And it's not perfect. But that's how the world should work. It can help. It can help that it doesn't. So do you think that's clear? It's clear to me. Okay, if anyone doesn't think it's cool. Great. All right. So then I usually do a command s to save. Great. Then I come back into tower. And I go to working copy. And it will show up here that I've got something that I've changed. And then I do a subject line updating. So small thing, the updating is kind of redundant. It's a commit message. So you're updating something. So just just say what you want, want to achieve. Yeah, that's great. After hitting commit, I go back. This is still the lead branch. I right click and then push revision. Should I be doing publish instead of push? Nope. Push sounds fine. I don't know what publish is. Back when I used to do this stuff, when I was a Cisco, there was a push to staging, and then a push to production. So I wasn't sure if they're if that's kind of the that that's what you do locally, you have a staging area locally. So maybe push publish generates the merge request, that will be nice. If you do it by the command line, get what will just send you a URL where to create the merge request. Let's see when this is over, if there's a merge request, if not, then I'll publish it and then we'll see if that creates a merge request. Good idea. It's pushed, but it says it's updating a local there it is right there. Create the merge request this way. You're seeing that if I had done publish, then maybe the merge request already would have been Yeah, you come directly, you click that URL, you come directly here. So no need to navigate to gitlab.com. No need to press the blue button. We can do it. Let's bury. Let's do this. This was just a thought. Let's let's finish this. It's fine. Because I'm very unsure whether publish will do that. So we start time and I say remove source branch, right? Yep. I'm applying it to you said. Awesome. Cool. And I've set it to update. So we're done. You want to show me how you do it? Sure, we can I can do that. That's interesting. I don't have anything on my desktops. I don't know which one I'll be sharing. So I should be sharing this one. What I would do. So open it. I think it was handbook communications. I won't type it out full. I'll just say first letters and then it's this one. And to find the chat part, I'll type a hash and then chat space and then chat. So I'll find the right section immediately. Still do need to pull. I do that with GL. I have that set up as an allies in my dot files. And what what what tool are you using to do this? So this is Visual Studio, Visual Studio code. And Barbie's improvement is not yet merged, because it's still testing. So I'll just make a tree here. And then I'll change it. No need for extra indentation. So GCA is also in the dot files and basically this commits all. So it first adds it. It's a commit with a hyphen a. And now with GP, I pushed it. And now I should see that magical URL I talked about earlier. And if you notice in the here in the in the bottom, you can see Oh, and I push directly to master. So now the website is improved. So I do this a lot. And the advantage of being CEO, you can push directly to master. But suppose you don't have those rights, you might, you might want to do something different. So let's look, let's make another change. Even if I had the rights, I still kind of like the I did it, I get a chance to review it first. Yep, makes sense. So I went to another branch. I commit like indentation after a title, something we'd like to see, push that the indentation after title isn't needed, but it's according to our guidelines. And I think it looks prettier. We still have to make a job. And then here is it. I press I felt there was command. Yes, best commands. And I can I'm then I go to a browser. Hey, this doesn't work. This would work in my iterm. But this doesn't work yet in Visual Studio code. And I have no idea why that is. So would you say that using Visual Studio code as better for people more comfortable coding, and maybe tower and Adam is better for people who are less comfortable coding? Or do you think that someone who is less technical should feel just as comfortable doing it your way? I think Visual Studio code is yeah, it's just harder. It's harder for everyone to use stuff on the on the comment line. Does it matter where you're from? However, like, like using it, it's, it's, it will be faster. So you kind of have to invest a bit of time and then make it faster after all. By the way, if you wonder how you get a terminal, it's control tilde, you can create a terminal in Visual Studio code. So it's, it's not about this is for those people, this is for those people, it's kind of in using the comment line of Visual Studio code, it's kind of a time investment in order to be more effective. And one thing is in towers, sometimes you cannot do certain things you can. So for example, you want to cherry pick something that that tends to be hard. So it's easier to begin. But then when you have to transfer to do something complicated, it's much harder in because then you have to make the transition to comment line and do something difficult at the same time. And that's super hard. So you, you'd rather be working from the comment line the whole time, and not not have to make the transition when you have to do something hard. And like if you, if you do hand to do something hard and get your Google, you'll find a Stack Overflow thing, you'll try that command, and then that command is not going to tell you how to do it in towers. So I think for our team members, it's probably after their first initial steps, it's probably worth the investment to to learn the comment line and then use Visual Studio code, a proper editor. Okay, all right. But thanks, Barbie. I'm looking for an easy way out. There's there's no easy way out. But hey, you're you're already effective, you're already doing it yourself. I that's good enough. And it's not that you have to to use Visual Studio code, or otherwise you're doing it wrong. And some of the things we've we've made in GitLab are because our own team members complained, like for example, they had to resolve merge conflicts, and we're like, yeah, use an editor. And they're like, I don't I want to use the online editor, and we're like, okay, that makes sense. We'll fix it. So so we've we were the first Git software where you could do a merge conflict, resolve that online, and still proud of that. And that's because our own team members complained. So it's not the answer shouldn't be use this tool. The answer should be how can we how can we change GitLab to make it easier for you? Okay, excellent. Thank you, Sid. Cool. Thank you, Barbie.