 Hi, I'm Ty Davis you may remember me from the film last night's release and today we agile tomorrow. We dev ops Enabling and fostering collaboration among team members helps streamline the automation of repetitive tasks Tracking assets and workflows of source code management is the top team priority Weekends are very convenient if you don't want to keep your documentation and your repository But you do want to keep it in the same project where your code resides Or if you want it in both locations You can create wiki pages in the web interface or locally using git since every wiki is a separate git repository as it is built right into each git lab project Supporting all product assets and workflows is crucial because modern projects include a wide variety of digital files From designs to images and even multimedia files The system must support managing and tracking the assets and workflows of all team members or teams In addition to the source code So git lab manages designs and graphics such as images audio and video binaries of multiple formats Providing one tool for all the different digital product teams and team members Allows for less friction in the different workflow Code of view is really where the core of development happens Engineers write features and then they push them up to git lab for a code review and ultimately to merge them into their master Development branch or whichever branch they use an overview of the merge request gives us a holistic view of changes made Branches reports and access to a web IDE Individual merge requests allow the opportunity to have open discussions around the changes being made or proposed Often multiple discussions are occurring around a change and having the ability to open a thread around a specific comic keeps discussions clean and sortable When we want to provide feedback around specific code changes with an engineer not having a central location to collaborate Leads to extended delays as feedback must be applied separately from the code Snippets allow teams to use routinely required content from a catalog of repeatedly entered code Often this is justified because the content varies only slightly or not at all each time it is entered With git lab snippets you engage in a conversation about that piece of code facilitating the collaboration among users While reviewing changes a clean file tree quickly allows for navigation between lines of code that have only been affected by the changes Collaborating around specific code changes provides immediate feedback to the engineer by editing specific lines of codes and proposing it as a suggestion By building up an audit trail of every single discussion We create a great way to enable collaboration and feedback the result and being more efficient and having immediate actionable item Once all discussions are resolved teams or individuals can look to merge that specific MR concluding work on that branch and closing the related issue Be sure to check out our next videos and continue our conversation around source code management