14 using different applications to create one final webpage

.github/ISSUE_TEMPLATE/completed-lists.md

@@ -2,7 +2,7 @@
 name: Completed Lists
 about: This is for your master pull request to merge your master into this repo.
 title: Put your UCID as the title (replace this text)
-labels: Compiled List
+labels: ''
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/master-pull-request.md

@@ -0,0 +1,15 @@
+---
+name: Master Pull Request
+about: This is for your master pull request to merge your master into this repo
+title: Put your UCID as the title (replace this text)
+labels: Complied List
+
+about: This is for your master pull request to merge your master into this repo.
+title: Put your UCID as the title (replace this text)
+labels: compile list
+
+assignees: ''
+
+
+
+You need to make a pull request and add the link to the pull request to this issue when you submit.

.github/ISSUE_TEMPLATE/things-i-don-t-understand.md

@@ -2,7 +2,9 @@
 name: Things I Don't Understand
 about: This is for adding issues that you don't understand
 title: ''
-labels: Things I Don't Understand
+labels: Complied List, Things I Don't Understand
+labels: IDontKnow
+labels: Complied List, Things I Don't Understand
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/things-i-learned.md

@@ -2,9 +2,17 @@
 name: Things I learned
 about: Add one item for each thing you learned keep to max of 255 characters
 title: "[Things I Learned]"
-labels: Things I learned
+ 2-ssh-keygen-and-github
+labels: ''
+
+labels: IKnow
+
+
+
+labels: ''
+
 assignees: ''
 
----
+
 
 Please add one item that you learned.  File new issues for each item that you learned.  Please keep the number of characters to no more than 255.

.github/ISSUE_TEMPLATE/things-i-want-to-know.md

@@ -1,10 +1,34 @@
 ---
+name: Things I want to Know
+about: Describe this issue template's purpose here.
+title: Thing I want to Know <file in title> [Thing I want to Know
+labels: Things I want to Know
+
 name: Things I want to know
 about: Describe this issue template's purpose here.
 title: 'Thing I want to know: <file in title> [Thing I want to Knows]'
-labels: Things I learned
+labels: IWantToKnow
+
+
+
+name: Things I want to Know
+about: Describe this issue template's purpose here.
+title: Thing I want to Know <file in title> [Thing I want to Know
+labels: Things I want to Know
+name: Things i want to know
+about: Describe this issue template's purpose here.
+title: ''
+labels: Things i Want to Kno
+
 assignees: ''
 
----
+
+
+Please describe what you want to know in less than 255 characters
 
 Please describe what you want to know in less than 255 characters.
+
+
+
+Please describe what you want to know in less than 255 characters
+

README.md

@@ -13,17 +13,20 @@ The purpose of this assignment is to practice collaborating using GIT/GitHub and
 
 ### Your list should look like this:
 #### Things we understand**
-1.  Python Print[1]
-2.  Linux Directory listing[2] 
+1.  Github repositories[1]
+2.  Github classroom assignments[1] 
+3.  Autograder[1]
+1.  GitHub repositories[1]
+2.  Linux Directory listing[1] 
 3.  Docker Installation[1]
 #### Things we don't understand
-1. Git Stash[1]
-2. GIt pull[2]
-3. GIT status[1]
+1. Simple and well explained definitions needed[1]
+2. Simple explanation of what everything is used for[1]
+3. Explain Pycharm terminal and commands[1]
 #### Things we want to know next**
-1.  Elastic Search Indexing [1]
-2.  Cloud deployment with Kubernetes[2]
-3.  Teraform[1]
+1.  Understand and comprehend process[1]
+2.  What and how do they do and work[1]
+3.  Clear vocabulary[1]
 
 ## Prerequisite - YOU. MUST SETUP PRIVATE PUBLIC KEY AUTH WITH GITHUB OR YOU WILL GET ACCESS DENIED ERRORS WHEN YOU PUSH FROM THE TERMINAL
 Add your ssh public key to github - See video
@@ -63,6 +66,45 @@ To submit this assignment you need to submit the result of step #5 to canvas.  W
 Collaborating on GitHub:
 
 1. Fork the repository: Each person should fork the repository to their own GitHub account. To do this, click the "Fork" button in the top-right corner of the repository page.
+
+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.
+4. Go to the "Project" board, and if you see any tasks without a status move them to the todo column.  
+5. Pick one task and move it to the in progress column to indicate you are going to work on it.
+6. 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. 
+7.  Do a "git checkout <name of branch>" i.e. "git checkout 1-some-issue".
+8.  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.
+9. Push the branch back by doing a git push origin head or use the push command from the drop down in Pycharm.  
+10.  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.
+11.  Check the documentation board and you should see that the task has moved from in progress to done.
+12.  Once you have resolved an issue you should go to your partners' fork and make a pull request that to merge your issue branch.  
+13.  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.
+14. Once your partner creates the issue they need to merge the pull request and close it with the "closes #?" in the merge message.
+15. 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 so I don't need to login with a password
+2. I learned Github issues
+3. The importance of having Docker running.
+### Things you don't understand about what we are doing / web development.
+1. I wish I knew how to read different errors on command line.
+
+2. The purpose of Github Actions.
+3. Resolving merge conflicts.
+
+
+### Things you want to know next
+
+1. Using different applications to create one final webpage.
+
+1. How to connect viewjs to elastic search
+
 2. Enable issues: If you don't see the "Issues" tab in the main menu, you should enable it in the repository settings. 
 3. 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.  
 4. Go to the issues tab you should also create labels for "I Know", "Want to Know", "Don't Understand", and "Master List".  
@@ -92,3 +134,55 @@ Collaborating on GitHub:
 13.  update your local main branch with the changes from the merge by doing git pull origin main
 14. Repeat again, and again, and again
 
+
+
+
+
+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.
+4. Go to the "Project" board, and if you see any tasks without a status move them to the todo column.  
+5. Pick one task and move it to the in progress column to indicate you are going to work on it.
+6. 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. 
+7.  Do a "git checkout <name of branch>" i.e. "git checkout 1-some-issue".
+8.  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.
+9. Push the branch back by doing a git push origin head or use the push command from the drop down in Pycharm.  
+10.  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.
+11.  Check the documentation board and you should see that the task has moved from in progress to done.
+12.  Once you have resolved an issue you should go to your partners' fork and make a pull request that to merge your issue branch.  
+13.  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.
+14. Once your partner creates the issue they need to merge the pull request and close it with the "closes #?" in the merge message.
+15. 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 so I dont need to login with a password
+2. I learned Github issues
+3. The importance of having Docker running.
+### Things you don't understand about what we are doing / web development.
+1. I wish I knew how to read different errors on command line.
+2. The purpose of Github Actions.
+3. Resolving merge conflicts.
+### Things you want to know next
+1. Using different applications to create one final webpage.
+2. Becoming more comfortable with Docker.
+3. Learning how to use other applications that are needed in the field.
+
+
+
+1. I know how to make an SSH key and add it to github so I don't need to login with a password
+2. learned github issues
+3. how to do a commit and push on pycharm
+
+### Things you don't understand about what we are doing / web development.
+1. Need help on the assignments
+2. Need help with the commands on pycharm
+3. Some of the terminology used in class.
+### Things you want to know next
+1. How to merge and resolve merge conflicts.
+2. Understanding how pycharm, github and docker go hand in hand.
+3. Learn more about dockerhub