Lab4_Starter

For this section of the lab we would like you to:

1. Click "use this template" in the upper right corner of the repo to clone it into a separate repository
   1. DO NOT fork the repository
   2. Make sure you are NOT trying to push your fixed code to the starter code repo.
2. Create an new branch named lab4-fix. to fix the buggy code in the scripts folder.
3. After you have fixed the buggy code, we would like you to create a pull request to the main branch of your repository not ours which will cause the pipeline with automated tests to run.
   1. IF you accidentally forked this repository instead of cloning it ake sure you are creating a pull request to the correct repo.
   2. Any pull request made to the starter repository will be deleted.
   3. You will lose points if you make a pull request to the starter code repo instead of your own repo
4. Wait for the automatic tests to finish running.
5. If all is done correctly, you will get a green checkmark saying ready to merge! It should also say "All checks have passed." Please take a screenshot of this checkmark. (Make sure your github username is somewhere in the screenshot)

Details

The changes will be fairly simple, and shouldn't take much time. The main reason for this section is to get familiar with what creating a pull request looks like. More specific, the process of what passing automated testing looks like when trying to create/merge a pull request. For instance, first try adding a comment as your change and then create a pull request. What happens? We want you to be familiar with this process since it is a part of what we call a pipeline. Pipelines are in place to try to prevent poorly written code going live (main branch). Having a pipeline is a crucial part of software engineering.

Bonus Question(No credit)

How could have this buggy code gotten into the repo, if the pipeline was already in place?