I actually forget about one since it's I want to share with you and I'll put it between. Second Wagner. I want to present you our portfolio. It's called peak flow flow, because it will give you more clear understanding of how merging process and branching works. And get flow. It's a pretty useful workflow to use when you code together with other team members.

And you may have like a great organization of features that you can have, or maybe want to, at some places, fix bugs and other so get flow. It's also the topic to talk and I just want to touch on A small piece of it. And just to show you an organization, how you can water the position you might have, if you learn about it flow and supplemented into your project, and unless you were to Google this term and explore it a bit more, because it's very useful for developers, and it's simplify life. Very easy, just another nother type of disciplines that you might have and you'll see how it goes together on the same repository. This workflow give you an ability below, as an example of how simple get flow branches, tree may look. As you can see here, all of this names are actually French name so slash is also separate.

So master branch develop branch feature branch and I put it here like an organization. So it's pretty easy to separate since with gates and for example we have main master is our untouchable production range a range where all senses really work at the tested approach here and measure the lipids like place for the libres where they can have a one foot base and collaborate together and feature slyke a separate feature branch with some changes where I wonder what we can work on. And as you can see, feature changes a have to Charles like, fix improvements and fix implement. And she is another feature branch with different Instead of changes and have two branches it's people create for. And then box. As you can see here, it's actually can be stated like, if you have a task tracker, and your project manager or your tester, find some bugs in your project, you may have create an issue for it.

And it's actually a name and code for this issue. And it's pretty useful when you find some bug, and you're just working on it, you create separate branch. When you try to fix this back end, you put also your branch name, your support, and Id for your issue. So it's really pretty easy for your team, to review code, maybe project manager and you cannot actually Moses issue. If you put some some aliases into your witnesses, we can talk about it but it's better not to touch right now. Okay, so I think it's pretty easy.

And it flow. It's a great current process. It's gonna require some practice, but it will really help you to understand since like, it merged in each rebase and says, Okay, we'll talk more about the merge in the next slide.