This Repo is to deliver the CS Tech exercise Content
**Problem Statement: ** "Our security team is asking for help ensuring proper reviews are being done to code being added into our repositories. We have hundreds of repositories in our organization. What is the best way we can achieve at scale? We are new to some of the out-of-the-box settings and the GitHub API. Can you please help us create a solution that will accomplish this for our security team?"
**Background knowledge and assumptions ** _ You can create and use a new GitHub repository to develop and present the solution Assume you are the named GitHub contact for the customer. You will build and present the example to the customer GitHub has more than one API interface along with API libraries. Be prepared to explain the hows and whys in your design Technical guidance: Organization events and protected branches are useful features to help drive your solution. Also, don’t forget to check the GitHub Docs The first branch in a new GitHub repository will be created once a commit has been made. One idea is to have a README created with each new repository, so that the first branch is created Documentation is highly valued at GitHub__
Solution requirements
We are most interested in your approach, the mindset you apply, and how the solution is presented to your customer. The technical solution to accomplish this is to listen for organization events to know when a repository has been created. When the repository is created, please automate the protection of the default branch. Notify yourself with an @mention in an issue within the repository that outlines the protections that were added.
Some things you will need:** ** _A GitHub account An organization (you can create one for free) A repository to store your solution/presentation. We will look at this together in our next conversation A component that listens for webhook deliveries. We don’t require a specific technology/runtime, use languages and tools you are already familiar with We strongly recommend using languages and tools you are already familiar with. A README.md file in your web service's repository that documents how to run and use your solution. _