Provide a short description explaining the what, why, and how of your project. Use the following questions as a guide:
- What was your motivation? - To further increase my knowledge of coding.
- Why did you build this project? - To gain a basic understanding of what we will be doing during the bootcamp.
- What problem does it solve? - Helps answer any questions we had before starting the bootcamp.
- What did you learn? - I learned how to use VS code and git bash commands.
If your README is long, add a table of contents to make it easy for users to find what they need.
What are the steps required to install your project? Provide a step-by-step description of how to get the development environment running.
N/a
Each section of our notes pertain to a certain topic we're studying. We learned basic commands for within each topic
N/a
The last section of a high-quality README file is the license. This lets other developers know what they can and cannot do with your project. If you need help choosing a license, refer to https://choosealicense.com/.
Please refer to the LICENSE in the repo.
🏆 The previous sections are the bare minimum, and your project will ultimately determine the content of this document. You might also want to consider adding the following sections.
Badges aren't necessary, but they demonstrate street cred. Badges let other developers know that you know what you're doing. Check out the badges hosted by shields.io. You may not understand what they all represent now, but you will in time.
If your project has a lot of features, list them here.
If you created an application or package and would like other developers to contribute to it, you can include guidelines for how to do so. The Contributor Covenant is an industry standard, but you can always write your own if you'd prefer.