2. Enable issues: If you don't see the "Issues" tab in the main menu, you should enable it in the repository settings. Go to the "Issues" tab, and click "Milestones" to add a 0.1.0 milestone and describe it as a consolidated list of issues from your team. On the issues tab you should also create labels for "I Know", "Want to Know", and "Don't Understand". Once you create these labels then go to settings and look for the "Issues Template" and create 3 issue templates that will provide the starting text for each issue filed of that type. At the bottom of each issue you will see that you can automaticly assign a label to that issue type, so connect the respective labels you created with the 3 issue types.
3. Create one issue per item in your list and assign it to the correct issue template.
4. Create a new project tab and create a new project (you have to click the down arrow next to "link project" to change it to new project). When you create a project you need to select "board" and name it "Documentation Tasks".
5. Go back to your issues, click on each issue, and assign the issue to the following: assignee i.e. you, miletone i.e. the one you created 0.1.0, project documentation (set the status to todo) and create the branch for the issue.
6. Go to the "Project" board, and if you see any tasks without a status move them to the todo column.
7. Pick one task and move it to the in progress column to indicate you are going to work on it.
8. If you have not done so already clone the repository to your local and type "git fetch" to see the branch(s) for the issues you created.
9. Do a "git checkout " i.e. "git checkout 1-some-issue".
10. Complete the issue by adding one item to one of the 3 categories. Do a git status and make sure that only the readme is changed. If the readme just has the change then you can do a git commit -a -m "PUT A DESCRIPTIVE MESSAGE HERE". git commit with the -a flag adds all the new and modified files to the commit.
11. Push the branch back by doing a git push origin head or use the push command from the drop down in Pycharm.
12. Make a pull request (MAKE SURE YOU DO IT FOR YOUR OWN IT WILL DEFAULT TO MAKING A PULL REQUEST TO THE UPSTREAM REPOSITORY" for the branch and when you come to the part where you have to need the commit message you have to add "closes #?" the ? is whatever issue number that the pull request resolves.
13. Check the documentation board and you should see that the task has moved from in progress to done.
14. Once you have resolved an issue you should go to your partners' fork and make a pull request that to merge your issue branch.
15. Your partner will then need to create an issue to merge the pull request. You first need to save an issue and after you save it will make the right side controls active and you can select the repository / pull request you want to link and fill out the other fields like assigning the task to the milestone, assigning a developer, assiginging it to the right project with the todo status.
16. Once your partner creates the issue they need to merge the pull request and close it with the "closes #?" in the merge message.
17. On your own fork, you will want to make a pull request to yourself to merge their updated master into yours.

Complete the Assignment By adding your issues to these 3 lists.

Put your items here

Things you understand so far

1. I know how to make an ssh key and add it to GitHub.
2. I learned all about GITHUB Issues
3. I learned how to create and name repositories in Github and in Docker.
4. Resolving Merge Conflicts [1]
5. Pull Request[1]

Things you don't understand about what we are doing / web development.

1. What some git commands do.
2. I don't understand what exactly a DevOps Engineer does.
3. I don't know how to fix some merge issues.
4. GIt Track[1]

Things you want to know next

1. I want to know more about Docker and its functions.
2. I want to know how what we're learning will be used in web development.
3. I want to know if it's possible to use the terminals of other IDEs to do git commands.