This week, you will be going through steps to set up tools needed to be successful in this camp. If you are already familiar with some, feel free to skip to the end and complete the task to move on.
[ ] 3: Add a paragraph introducing yourself under the About Me section in the blog.md file in root.
[ ] 4 Commit the change to test, make a draft pull request to your main branch, naming it Adding self introduction and add a detailed description of your contribution. Then, click Ready for Review and merge the pull request once the CounselorBot approves it!
💡 Tip: You will only need to make a draft pull request for Week 1 Step 1. For the rest of the curriculum, you may create "regular" pull requests!
Making a Draft Pull Request
❓ When you're collaborating on GitHub with other developers, sometimes you might want to make a draft pull request before your code is ready to be reviewed! We can simulate this with the CounselorBot, and we will only be doing so with Week 1 Step 1.
Instead of clicking Create Pull Request, click the drop down arrow and click Create Draft Pull Request. Then, click Ready for Review. This allows the CounselorBot to review your pull request to check if you're ready to go!
What is GitHub?
GitHub is a industry-standard platform allows developers to save and collaborate on code. You can use GitHub to manage your files, changes in your project, version control (the ability to revert back to previous versions of your code as well as versions developed by other programmers), and more.
Check out "The Github Flow" for more information on issues, pull requests, committing, and branches!
If you want to learn more about what it is and how to use it, try taking this GitHub Learning Lab Course. After finishing it, you will have a strong understanding of all the features GitHub has to offer.
✍️Vocabulary
#### ‼️ Repositories
Repositories (or repos) are essentially **folders where you can store files of code.** The repo of our camp was duplicated into your account when you clicked "Create Template" so that you can commit changes and complete each lesson.
#### ‼️ Issues
For our camp, each week is placed inside an issue. Only when you complete the week (committing the necessary code and commenting), will the issue close and you can move on to the next issue. Don’t worry – committing changes is easier than it sounds.
> 💡 *On usual repositories in the contributing world issues are tasks or bugs that need to be completed or fixed.*
#### ‼️ Fork
If you want to contribute to someone else's code, you would "fork" it. This creates a copy of the code under your account that you can make changes to. Create a fork when you **want to make changes to someone else's code and contribute to it.**
#### ‼️ Branch
Creating a **branch** on a repository is like forking a repository. You would do this when you **want to make changes to your code without harming a working version.**
#### ‼️ Pull Request
Once you make changes on **a forked repository or another branch,** you might need to bring the changes into the "main" repository. This allows YOUR changes to be visible in the main project! *You are basically asking for permission to "merge" your changes."
**This allows you to:**
⭐ Collaborate on code
⭐ Make comments
⭐ Review the contributions made
#### ‼️ Command Line Interface
A Command Line Interface (CLI) is your computer's visual application for accessing its operating system. There are different types of CLIs for different operating systems, such as Terminal for MacOs and PowerShell for Windows. If you have Windows, make sure to also install [Git Bash](https://git-scm.com/downloads) for a better tool. In upcoming issues, we will refer to your CLI as your Terminal or Command Line, but remember that they mean the same thing!
Key functions you should be familiar with after this task include:
Committing changes
Forking a repository
Making a new branch
Making a pull request
❓ What do all the emojis mean?
Glad that you asked!
| Emoji | Meaning |
| --- | ----------- |
| 💡 | Helpful tips |
| ‼️ | Important info |
| ❓ | Question you may have |
| ⭐ | Features |
Week 1 Step 1 ⬤◯◯◯◯◯◯◯◯ | 🕐 Estimated completion: 5-20 minutes
GitHub
This week, you will be going through steps to set up tools needed to be successful in this camp. If you are already familiar with some, feel free to skip to the end and complete the task to move on.
✅ Tasks:
test
.About Me
section in theblog.md
file in root.test
, make a draft pull request to your main branch, naming itAdding self introduction
and add a detailed description of your contribution. Then, click Ready for Review and merge the pull request once the CounselorBot approves it!Making a
Draft
Pull Request❓ When you're collaborating on GitHub with other developers, sometimes you might want to make a draft pull request before your code is ready to be reviewed! We can simulate this with the CounselorBot, and we will only be doing so with Week 1 Step 1.
Instead of clicking
Create Pull Request
, click the drop down arrow and clickCreate Draft Pull Request
. Then, clickReady for Review
. This allows the CounselorBot to review your pull request to check if you're ready to go!What is GitHub?
GitHub is a industry-standard platform allows developers to save and collaborate on code. You can use GitHub to manage your files, changes in your project, version control (the ability to revert back to previous versions of your code as well as versions developed by other programmers), and more.
Check out "The Github Flow" for more information on issues, pull requests, committing, and branches!
If you want to learn more about what it is and how to use it, try taking this GitHub Learning Lab Course. After finishing it, you will have a strong understanding of all the features GitHub has to offer.
✍️Vocabulary
#### ‼️ Repositories Repositories (or repos) are essentially **folders where you can store files of code.** The repo of our camp was duplicated into your account when you clicked "Create Template" so that you can commit changes and complete each lesson. #### ‼️ Issues For our camp, each week is placed inside an issue. Only when you complete the week (committing the necessary code and commenting), will the issue close and you can move on to the next issue. Don’t worry – committing changes is easier than it sounds. > 💡 *On usual repositories in the contributing world issues are tasks or bugs that need to be completed or fixed.* #### ‼️ Fork If you want to contribute to someone else's code, you would "fork" it. This creates a copy of the code under your account that you can make changes to. Create a fork when you **want to make changes to someone else's code and contribute to it.** #### ‼️ Branch Creating a **branch** on a repository is like forking a repository. You would do this when you **want to make changes to your code without harming a working version.** #### ‼️ Pull Request Once you make changes on **a forked repository or another branch,** you might need to bring the changes into the "main" repository. This allows YOUR changes to be visible in the main project! *You are basically asking for permission to "merge" your changes." **This allows you to:** ⭐ Collaborate on code ⭐ Make comments ⭐ Review the contributions made #### ‼️ Command Line Interface A Command Line Interface (CLI) is your computer's visual application for accessing its operating system. There are different types of CLIs for different operating systems, such as Terminal for MacOs and PowerShell for Windows. If you have Windows, make sure to also install [Git Bash](https://git-scm.com/downloads) for a better tool. In upcoming issues, we will refer to your CLI as your Terminal or Command Line, but remember that they mean the same thing!Key functions you should be familiar with after this task include:
❓ What do all the emojis mean?
Glad that you asked! | Emoji | Meaning | | --- | ----------- | | 💡 | Helpful tips | | ‼️ | Important info | | ❓ | Question you may have | | ⭐ | Features |📹 Walkthrough Video