 All right. Hello, everybody. This is Andrew Connell. I'm sorry for a little bit of the hassle. If you were just trying to tune in on that, I was trying to get everything all set up the right way and I was having a little bit of a trouble here with my computer. So sorry about that. So here's what I want to do today. I want to take a few minutes and show you how to go about doing the best way that you can go to customize or to submit a change to the SharePoint documentation on the SP Dev Docs. It's a very common thing that you see people wanting to be able to do and this is just something that is it's just a it's just something we want you want to be able to do and it's just a common thing. So I want to show you kind of what the experience is going to be like with this. So what I'm going to do is if you first come over here and you take a look at an open issue that I have, I just created this issue a minute ago and I assigned it to myself and I'm going to spare you kind of the details of what this is saying. But effectively, whenever there's a push or whenever there's changes to the docs, behind the scenes, there's a build process that happens at Microsoft for the Microsoft build docs. And if you are one of the people who manages the repository, which there's a few people that do it. I'm one of the ones that also handles this SP Dev Docs issue list. We if there's any errors, we get email notifications when there's a build a problem with a build or something like that. And so what lately and I've noticed in the last couple of days, a couple of documents have gotten have some minor issues with them like and when I say minor, I mean, they're like really small little problems. And there's not nothing that you would notice a difference of. I'll show you the kind of error report that we get is you see like we get what I'm showing here on the screen. Let me make that look bigger. Actually, I got to show you the screen, I guess. I said I was going to show you the screen now I show you the screen. Alright, so this is what we normally get. So here's the issue that I was talking about a second ago, 5647. And I've gone there and I've listed out all the different problems that we have with the docs that we're going to fix in just a minute. This is where I got that error report. And so it's telling me a bunch of different problems. Now some of them are really easy to figure to fix. So like for example, if you're watching this, you may be aware of the fact that there are some some of you have have gotten a note an email back from me or a comment back for me that you need to remove the locale from a URL. So like in this case here, you'll see where it says for localization, you should remove the the locale to any link that points to any Microsoft site. And the reason for that is because Microsoft's front end is detecting the locale of the current of the request of the current user. And it's going to put the locale in to the URL that redirects them to the site if it's been localized. Otherwise, it sends them to the default the ink on default English, but you shouldn't use the locale, you should let let Microsoft figure out where the person should be redirected to. So these are just some of the things that we're going to fix. We'll go through each one of these in just a minute. But the way you want to do the way we want to do this, though, when you want to make changes to the docs is that you're going to come up here to the main repository and you want to create a fork of this. And what that's going to do is that's going to create a copy of this repository in your personal GitHub account. And so that's what I've done. So notice here in the URL, it's SharePoint slash sp dev docs. Well, on my GitHub account, it's Andrew Connell slash sp dev docs. And in this fork, what this is doing is that this is going to allow me this is allowing me to see the to have a copy of the entire repository so that I can see what's going on. This is where I'm going to make my changes. I'm going to make my changes and submit them back to my fork. And then once I've done that, I'm going to go submit a pull request to the the Microsoft owned repository. And that rep and I'm going to that pull request is effectively asking somebody from Microsoft to say, I've made some changes. I'm requesting that you pull those changes from my repository and put them in yours. So that's the that's the final outcome of what we really want to have happen. Now, in order to do this, one of the things that we end up having to do is I need to make sure that my fork is in good standing. I want to make sure that my fork is really a complete copy of what's up in the Microsoft repository. And right now I can tell that it's not I intentionally waited a couple days because I wanted to want you to see this. If you go to your fork and it says that your master branch is 34 commits behind master, that's bad. It's easy to fix, but that's bad. And here's why it's bad. So let's say that this is the Microsoft repository. And it's got all the history down here, but then it's got a bunch of other things up here. Right? If I create a fork and it was based off the repo right here, and I'm going to start making changes here and I add my change like this. Well, there's all these other changes that I don't know about that when I submit my change, I could create a conflict with one of those. So what you want to do is you want to refresh your fork. So I'm going to show you how to do this. Now the way you do it is you you're really going to it's going to eat. There's two ways to do it. One is just delete your fork and then recreate it. That'll give you a clean copy. The other way of doing it though is to refresh it is I want to pull everything from the Microsoft repo into this one. So let me show you how we're going to do that. What I've done is I've created a clone. I've cloned this repository to my laptop. So you see here is that here's the link to it and I went there and said copy that link and then I went to my laptop and I cloned it. So if I come over here, this is the repository on where that is. So I've got this saved on my machine at SP dev docs. Now this is a copy of the repository on my laptop and then I have another copy of it in my GitHub account and then there's a third copy of it at Microsoft and the Microsoft one is the main one. So I need to do all of my work local on my laptop, send those changes to my fork and then have those changes from my fork get sent up to Microsoft. So what I'm going to do is now that I'm down on my laptop, I want to pull all the Microsoft changes down onto my laptop and then push them into my account on GitHub. So how do I do that? So this local repository on my laptop, this is just a local repo. But what's important, what I want to focus on here is I need I want to make sure that the that I need to have a connection to these other two guys, these are called remotes. Now by default, whenever you clone a repo, my get sets up a remote called origin and that's pointing to the origin on my machine up on as pointing the origin up on my GitHub account. So the way I'm going to do this is come over here and if I say get remote and you can use different GUI tools for dealing with get I'm going to do everything command line because then it doesn't matter what tool you're using, these are all going to work. So I've got get remote set up and I'm going to do a dash V and what that does is that's going to list out all the remotes that I'm that I have on my machine. So by default, you're going to have that or sorry, I'm going to list out all the remotes in this repository that I have locally that I have in my my my repo. Now this I have origins already there upstream is one that I'd already created but you won't have that by default. What you want to be able to do now so visualize this what you're going to want to do is you're going to want to take your local laptop you want to pull all the changes from the Microsoft repository into your copy of the repo that you have in your laptop and then push them up to yours and that way your fork and your local and your laptop will be in sync with Microsoft. So how do you create that extra remote well generally speaking we have we create one called upstream and that's simply saying that you know here's my clone it's a clone of my fork my fork is a fork from Microsoft which is way up here. So Microsoft is upstream from me. So what I'm going to do is if I would go over I'm going to create another remote but we're not going to use it I'm just going to use the one that I already have I'll show you how to create it though. I'm going back to the original repo Microsoft's repo and I'm going to say I'm going to grab the link for this like I would normally clone it and I'm going to come back over here to my laptop and I'm going to say get remote add and we'll just call this the Microsoft upstream give it a name and then give it a link. So what that's going to do is that's going to create a new remote so we'll see that it created a new remote right here my called Microsoft upstream that points to the Microsoft repo. Okay so we got the first part done that's good the next thing that I want to do is I now want to go through and pull everything from the master branch in the Microsoft repo down into my local copy. So I'm going to do that by saying get fetch upstream that's going to say upstream that's going to say go get a picture of what's up there it doesn't download anything but it just says go get a picture of what's up there. Okay so it's getting a picture and now it knows about two new branches that have been created since I last did this. Now the next thing I want to do is I want to pull down everything from the master branch into my local machine so I'm going to say get pull from upstream the map everything from master. All right so it's going to pull everything from the upstream repository which is Microsoft's so sharepoint slash sp dev docs and I want to pull from the master branch into my master branch you can see there's my master branch right there so it just pulled all this stuff in now what I can do this arrow is telling me that my local repo is ahead of it is due for to have some stuff get pushed up to my origin so I'll then say get push now before I run this just take a quick peek here notice it shows that I'm 34 commits behind master or behind sharepoint master my master is okay so let's go back and let's run this command I'm going to push everything up it's pushing it up to my fork in my account and now if I come back over here and I refresh this page I should see my branch in my fork is now even with sharepoint master now that's good that means that now my stuff is a complete copy of what Microsoft has up in there in their repo that's good so how now what do I want to do well the next step is I want to go make my changes and the best way to do this is to go create a branch in your on your machine a branch in your fork that's going to contain all the changes you want to send to Microsoft you don't want to do it straight on master you want to do it you want to create a bench off master and make the changes in there so what I'm going to do is what was my issue again our issue was number 56 oh you know what I forgot to switch my demo over sorry about that all right so all I did let me go back and show you what I did here so what you see here is what you see here is I ran the get pull upstream that pulled everything back down and then after it pulled everything down down to my local machine I then said get push and it pushed all those changes up and once I did that if I come back over here to the browser you can see that now it shows that my branch is now even with master so that's what I was ultimately trying to get to okay so now the next thing that we want to do with this the next thing I want to do is I want to let's see where are we we want to go let we want to go create a new branch on our local machine so I'm going to come over here and say this this is I have uh it's issue number 56 47 okay so let's come back over to our our local machine and say get check out we're going to create a new branch called doc fix 56 what I just forgot it already 56 47 doc fix 56 47 that's just my style but you don't have to do it like that and now we go make our changes so let's go find some of the edits that we have here so we got a bunch of these localization ones these will be easy so we want the file introduction to share point business process integration so I'm going to come over here to vs code and look for business process integration there it is right there and I'm going to look for something called en-us yep there it is right there there's the there's that even us and we don't we just want to remove that so I'm going to delete that from that file and save our changes so that's one fix so I like to keep all of these commits nice and atomic but I'm going to do all of the localization ones at the same time so there's one in us one here's another one what is this this one is this is get connect to other services okay so connect to other services in your flow and we're going to look for just doing another search for en us sure enough there it is so we're going to remove that and I'm also seeing a couple other markdown formatting issues there that whoever wrote this has made a mistake so let's go through let's clean that up oh man there's a bunch of them again we're going to we're going to actually you know it will come back we're going to fix that in a separate one one thing we do have to do though is I need to make sure I change the date because the date here is telling us when the when the document was last updated that's important that's something that you will get pinged for if you don't if you don't do that you need to make sure that you put that you put the the dates in there correctly don't want one and where's the other one that we just did that one and this one's also got some problems okay let's see let's find another one in us we did that those aren't you in us here's one right here so bulk user profile update api so bulk user profile update api there we go find in us there's one right there and it looks like there are five of them so here's we're going to do we're going to look for all five of them let's see if it is let's see if they find it multiple places bulk update bulk update bulk update it found three of them okay there's there'll be five though so here's what we're going to do we're going to go and just remove those so we're going to move oh it found three with just in us all right cool so we're just going to remove those there we go those are all remove good save our changes so we got three files done so we got in us in us in us bulk and then here's another one we got here use theme colors okay let's find another one let's see use theme colors in your customizations find in us i can see there's one example there and we will remove that from right here all right all right got anything else in us no that should be those that should be it so let's go through and let's commit those changes so i'm going to say remove locale from microsoft links per ms docs requirement now one thing that i'm going to do here is i'm going to add a comment and my comment that i'm going to add is going to reference my issue so i'm going to say this references 5647 and i'm going to put that pound in there and you'll see what that's going to do when i push the change it's going to link this commit to that issue automatically if i just do that pound link number there now the other thing we're going to do let's go fix some markdown formatting stuff that i can see that's wrong so let's get rid of trailing spaces they're supposed to be breaks between these that's supposed to be a break it's also supposed to be a break save our changes so you're good now use theme colors let's look for markdown issues oh it's a big article oh look at that we forgot to do this so this would be 04 30 2020 all right so let's just do a quick scan of markdown issues no these are all good uh let's look at this one now our date we forgot to do our date on this one even though i said we should do it so i'll do it now and ah check this out okay so here's a good one here's a good one to find um you should not use bullet points with uh bullets with numbers like this first of all they should all be together like this and you should have list ordered numbers at ordered lists as just like this the one one one one um if something needs to be indented then you need to indent it correctly so like and if i can go like this let's get rid of there we go so now you can see it's nice give me a nice little update here let's see import works um so that note looks good i'll keep scrolling down let's see if anything else these break lines are not necessary in fact they're not supposed to be there that video so there's a tag that they're using to go through and to do the special video link uh oh look at this there i see why they're doing some of these bullet points here it's because they screwed somebody has messed this up it's supposed to be all spaces no tabs right and that's one of the reasons why their bullets aren't aren't indenting correctly so we will fix that for them uh there's another one here let's go through and let's uh toggle word wrap so we will ah here we go and we just need to move it in one why is it doing like that yuck okay and then one and we'll do the same thing here pull it back put it in five this should be a one and see a lot of times people end up doing this they when they change their bullets like that to put numbers here it's because the numbers weren't rendering correctly and it's because they're not using the the correct style of indentation when you do that you need to have a double indentation like that to make sure that the numbers uh stay correct like that all right so we'll just keep scrolling through make sure everything looks good yep that looks good this br should not be there looks good cool little trick that i have i have a little editor here so this is uh what is it uh current format current so it'll go through and show it there we go makes it look a little bit more tably let's get rid of that let's get rid of that preview so we can actually see what we're doing here oh this is gonna i think this might cause a problem with us uh nope indentation's fine so we're good to that where are we oh we're night well we got a long way to go let me skip through this kind of quick ah see these these aren't going to be these these are not going to be indented well i guess the indentation is actually correct because there's no image there so those are fine those are fine yep oh double brake line shouldn't do that that yellow squiggly that's telling me that there's a problem with the um with their markdown well here's a bad one too that was a white space that had mixed tabs and spaces should not be doing this questions table done okay that one's good let's close that one and now let's look at this guy and yep more formatting issues should do that should do that um if you have an image that you're putting in here let's go through and let's do the rendering in this if you have an image they have to be um double indented to make sure they stay in continuity with the bulleted list and to make sure the list doesn't break up if you don't do that you have it like just one in then notice that my bulleted list is going three four five one and that's because the indentation was incorrect so you can fix that by just doing the indentation correctly and see a preview of the rendering same thing with this like see that guy right there that should not first all we you should not be using block quotes like that um they want us to instead to do a note so what we'll do is we'll do like this like that and so now the note shows up we'll get rendered the way it's supposed to be rendered fix that fix that fix that oh my goodness there's so much messiness with the markdown just give me go through this a little bit longer and there we go okay so that's a bunch of markdown issues that we just had to deal with and i think that's both yep that's everything so let's just go through and we'll just say mark cleaning up malformed markdown all right good so that's those are those updates now let's go over here and look at anything else we have so what about set up share point listen libraries first line of the section is not valid rendered as a block quote so invalid note section doesn't even tell me what line it is oh boy okay so set up share point site lists so set up share point site listen libraries is that the one listen libraries yep okay so oh man so there's some markdown formatting stuff there there's a problem right there see that that's not that's incorrectly done all right so this is amount this this document is all is screwed up in a couple different ways so first of all notice how this note it doesn't look it's not being indented correctly this should be indented with the with this with the correct version so this is all this is going to be markdown stuff that's we have that we have a problem with so we're going to fix these as we go and you're going to see the changes happen on the right side as I fix them so what we'll do every heading must be separated by a separate line now for these you shouldn't their notes are not supposed to be set up like this instead they're supposed to have the note is supposed to go on a separate line and this really should be indented correctly and if you do it like that then notice you get your bulleted lists are contiguous and you get a nice indentation the way it's supposed to be now let's get rid of these trailing spaces that's supposed to be a one that's a one and notice the difference here too notice how I have these two are going are adjacent but they're not with this and that's because if you're doing an indentation like this you need to have that extra break all right so do like that more bulleted lists okay there goes now everything should be cleaned up so now I see what that that rendering that note was not going to work that's what that error was that we were getting the first line is not valid it's because you should always have it say something like this excuse me all right so let's try this again so now now we've done that let's uh go commit this so we've got uh fix up up oh don't want to scream and that's docs and what this is issue number uh reference is 5647 all right cool so we got that so we will save our changes there let's look at the next one invalid link okay power automate create your first flow all right so create your first flow and more markdown issues man this stuff is this is common we see this a lot that's not right either even there's even misspelling oh we're gonna get a lot of stuff we're gonna fix up here don't know who did this one oh and there we go another note that's not the right format either all right we gotta fix these as we go um all right so first to fix these let's go add a note the right way so I have this little extension here adding a note should be like this notes should look like that and then indented like so and let's make sure that we can see them let's see all the renderings that were changes we're making so we see them on the fly all right so that looks good image shows up good good this is supposed to be a note as well we don't they don't want us doing um docs doesn't like having um random stuff random like uh block quotes so this way we do think we render them like this instead uh various we'll spell the word correctly that's not good for docs let's go back and find out who did this uh here we go again another note there we go let's see six no it should be a one again another note oh these can go together uh that's fine that's fine break it up those are three that's supposed to be four to be frank this is just sloppy oh my god another one three spaces supposed to always be four that's not correct and one now granted a lot of these things you won't you won't um you don't know until you do it the first time um so I shouldn't be so like judgy on this um but to be honest I mean I can tell this this was written by somebody on the product group and this should not have been able to get passed uh should not have gotten merged in now we gotta figure out what the problem was so the invalid link so set up SharePoint listen libraries so where's that link find share set up SharePoint listen libraries so let's find the article set up SharePoint listen libraries here we go so this is where the file is we can close our rendering our preview rendering of it and let's get the relative path for where this is where's SharePoint where was the link so set up SharePoint listen libraries and lists and oh wait is this one over here okay so here we go this right here so this is the path of where it's supposed to be okay so where are we in this where is this document copy the relative path oh yeah so they're backing way up we're in the exact same folder so this is where they even screwed up the name of this this is supposed to be you're not supposed to have spaces in this all right so we better find that because I mentioned the table of contents that's gonna be a problem too so create your first flow so it's create your space first so create dash your first dash flow nope doesn't worry it was in the table of contents either so I wonder how they were even getting to this page all right at any rate uh let's see so we are so this is the bad link right here so we're down here so we need to go up one two we don't need three and then we go back down into getting started setting up SharePoint listen libraries see where that is so we here's where we are we need to get so here's the common place where we are so I'm going to go up one level that's the dot dot that you see right here up another level dot dot so now I'm at this level right here so I'm going to go into getting started right there and then the article there listen libraries and that should actually point to md I'm not mistaken aren't links supposed to point to md dot md I think so let's try and find another one that's got a reference to it oh there is a link in the in the table of contents that was wrong all right we'll just do that all right so here we go we have let's say we had a fix broken links and this was references uh oh wait our issue that's right so references number 56 47 all right next thing we got to do what's the next one so we got where's our next issue we want to solve that we just did this one so now first line up that's getting another one power on SharePoint connector action triggers SharePoint connection connector action triggers watch this fix do do do do do do add spaces to all those before 30 more problems do do do do do no we don't want to do that so I think add breaks and we're going to separate that one do do do do I'm wondering if I'm the one that actually merged this in because this would have been I should have caught all of this before they did this that important is the problem that we're actually looking for because it had the tag on the same line and it's not they're not allowed to do that all right no limitations let's break it up how much more do we have to go oh we're at the very bottom thank goodness here we go and a lot of empty break lines are not necessary and then we will also get rid of trailing spaces and document libraries like that all right cool so this is again fix markdown issues per MS docs exceptions references issue number 5647 all right let's see this is list form conditional show hide list form conditional show hide something tells me the same person was editing these things oh we got a bunch of issues here all right so 430 all right these should not be on broken lines that bullet is not going to work with the way you had it these bullets are also not going to work let's do this kv so I can see a preview of this come on kv kv there we go all right so now I can see it all right so now here we go do we'll get rid of those empty lines in a minute there's the one there's the error report that we were getting right there this needs to be indented how let's don't know what kind of code that is can't really tell based on what they sent bullet list should be separate on separate start and in on separate lines this guy separate line can't tell the type of code with this oh it's just markdown it's just formatting for json all right so we'll save those changes and again we will delete all of the trailing spaces and this is going to be a fix up mark down rendering issues per ms docs exceptions references 5647 5647 all right we're almost done one last one use theme colors invalid link oh i just lost vs code open that back up what was that again use theme colors use theme colors in your customizations is that right in your customizations yep okay so we are looking for this file right here supporting sections fine supporting sections all right so this is what we're looking for here and it's looking for it in the dot web parts guidance all right so this is where we are so let's grab a little trick here grab the relative path let's see where we are and we are going to supporting section backgrounds so let's do there we go that doc is where we're going copy relative path here's where we are and that's where we're going and so it's sending us down into web parts oh so yeah it's definitely not a valid thing so we are up here we need to go web dash parts slash guidance slash support okay yeah so it's just a bad link so nobody just tested their links save that and I think if i'm not mistaken yeah we had made a change already so then this is going to be a fix up markdown formatting per ms docs exceptions and this is references 56 47 okay now we're done all right i made all those changes so now that i made all those changes what i'm going to do now is i'm going to come back over to my command line and i need to push all those changes up so if i do a git log dash one line we can see here's all of the commits at the very top of things that changes i made and i can see that that stuff is ahead of my fork master and microsoft's master so what i need to do is i need to send all these changes in my branch to my fork and i'm going to do that by saying get pushed but that's not going to work because there is no branch in my fork that matches the one that we're currently on so i could just do exactly what it tells me to do which is to say get push dash u which is a shorthand for saying set upstream push to origin a new branch called doc fix 56 47 g it now when that's done if i come back over here and look at my branch it should see usually catches it pretty quick but a little slow right there we go just did it it found that branch there you go found the branch that we just did so i'm going to say compare pull request compare and pull request and so now i can i'm getting the template that is provided whenever we do a new change from um share point whenever we do a new change on the sp depth docs so what i'm going to do here is i'm going to say resolve multiple errors reported from ms docs build and what this is i'm going to fill out the form don't delete this if you delete this we're going to kick it back at you and follow the instructions please so here i'm going to say it's a content fix it says delete this paragraph after reading so i'm going to delete it related issues this fixes 56 47 and notice right there fixed multiple build warnings i'll do that and get rid of the rest of this what's in this pull request explain it fixes multiple markdown errors reported by ms docs build um things like incorrect bullet point formats incorrect um block quotes incorrect note and important block quotes callouts broken links um locales present and microsoft owned links this guidance section i can ignore this because it says you can delete it after reading so there's nothing we need to do there i can preview make sure everything looks good yep now watch this when i create the pull request what that just did is it created pull request inside of the sp dev docs owned repo from microsoft and it said i'm i'm putting a request in for you to pull everything from the branch in andrew connell's branch called doc fix 56 47 and not only has it gone through and showed me all the all the the commits that are related to this but if you go back and look at our issue because i referenced though in each one of the commits that i did because i referenced this issue you'll see each one of those different commits are going to show up they're automatically linked and the pull request is linked as well and so now because um the build is running in the background right now this is what's going through doing a build check to make sure that there are no issues with the that are there any issues with the build so i'm going to wait for a second to see this come through while we're waiting should go pretty quick what does it say 1229 so it should be the next minute let me show you what this looks like when there's one of these errors in the in the build process let me open this up in a separate window okay so this is the one this is the email that i got when there was an issue with this all right so here it was succeeded with a warning and it so it showed that somebody made an edit to this to this document there was maybe nothing wrong with them but notice this build this docs publish report that's the error that that's the page a link to the page that i just showed you a second ago that contains um all of these build errors that you see here so i want to let this build finish i want to let this build finish before i actually go um try to run this all right before i actually merge this in is i want to i want you to see the report that comes back maybe there's something that we need to fix here now you wouldn't get this stuff you wouldn't see those errors that pop up because this build is going to be fine because all the contents there and everything works just fine what we need what would be nice is if these build errors from the docs team if they would show up as like breaking breaking broken builds and force people to fix this stuff so just gotta wait another minute or two we'll let this finish call 59 oh we're already past that now too the estimate is wrong let's refresh the page maybe it hasn't refresh the page hasn't gotten refreshed yet your past due is taking longer than you said it would microsoft we're waiting one of the reasons i'm doing this is because i'm trying to test out some of the live streaming stuff so i appreciate you guys like i made a mistake at the beginning hopefully last time i did this my audio was a little out of sync with my video and i'm hoping that got resolved there was a time earlier when the sync when the the stream got really bad ah sweet all checks have passed now let me go over my email let me see if i get an update over here with an update about oh there's another warning it looks like so we didn't get them all i have a warning on this one so let me let's go grab the link to this report and let's go take a look at it because this is something we want to fix this we didn't spend all this time do nothing all right so details we have an error invalid file link so it's just one problem we got all the way down to one so create this is introduction to share point business process invalid file file link so i made a mistake okay so okay so let's go back to vs code where are you code let's go find that file it's not that file and the article is create your first flow create your up there it is so because we changed the link to that to point to the correct link now we created a broken link because the last time that somebody had done this they used a space and it wasn't supposed to be a space all right so that's easy so we'll just say that is fixed broken link references same one ref your references pound 5647 now what's cool about this is because i'm still in the same branch when i push my change when i push my change up to my branch again okay notice you actually just already kicked it in there's the broken link there's the one we just did i didn't have it didn't have to go through and do a complete what is doing a complete rebuild but i don't need to wait for this one i know that this one's going to fix the problem um but because the pull request is asking the upstream repo to pull changes from my branch i don't have to go resubmit a new pull request because anything else i add to this pr is going to get included when they actually do the merge right so it's going to make things we can see how that's going to work so i can't merge it right now because none of all the checks haven't finished if i try to do it shouldn't let me do that well let me do that huh did okay cool i shouldn't have done that i should have waited but i know that that link was going to fix it um this merging stuff you're not going to have the permission to do that i can do that because i have permission to help manage this so see if i come back over here because i reference this the right way because i reference this issue in the in the pull request it automatically closed the issue because this pr because that pr got closed so it was closed in this pr cool awesome so now you've been able to see what and watching this you've been able to see how to go about doing a merge um let's switch back like this yeah so the goal here was for you to be able to see um how to correctly update the docs um you saw how to refresh your fork um and you also saw uh just the process of how i was editing things and making each thing an individual commit those different fixes um that i was doing so now what i'm going to do is i'm going to go back and find out who was writing those docs for flow and make sure that they don't make those in power apps and make sure they don't make those same mistakes um again so with that thanks a lot for sticking around and i hope you learned something from this i will see everybody later