 We understand not everyone can use GitLab for source code management, and so we've made GitLab's award-winning CI CD available to GitHub users. Let's take a look at how that works. You'll notice here that this particular GitLab project is already mirrored from GitHub. To get it to this point, we started with a new project in GitLab, and on the right side you'll notice CI CD for external repositories. Simply select the GitHub button and enter your personal access token to get a list of all your GitHub repositories. Once you've done that and selected which GitHub repositories you wish to add, you've now connected GitLab to GitHub. Here's my GitHub repository. It's a fairly simple Hello World style app using Spring Boot. Within this environment, I've already got a few branches and pull requests going, and if we check in on one of these merge requests, what you see is that all the checks have passed. When I expose the checks, what you see is the GitLab logo. So in this particular case, when the pull request was created, GitLab's CI was run against the code, and if I click Details, it will actually bring me directly into GitLab. Notice I'm back at the Spring Boot test project where the build, code quality, and security scans have all run successfully. In this particular case, you'll notice if you're currently a GitLab user, some of the differences in the left-hand menu. Issues and merge requests are not present when using GitLab with GitHub. The assumption is that you would use GitHub issues and GitHub pull requests in place of those products. Thanks for taking the time to watch this.