From 5cf0ae11a6cca036f420c392eb41f80d3b8ec8cc Mon Sep 17 00:00:00 2001 From: Eric Li Date: Wed, 4 Sep 2019 16:47:07 -0400 Subject: [PATCH 1/4] Changed activity list to a to-do list --- README.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index 3b21c11..b2903ba 100644 --- a/README.md +++ b/README.md @@ -5,15 +5,15 @@ A repo to play with the common git operations in and learn how to get working wi - Desktop app (optional, very useful for development) https://desktop.github.com/ ## Steps to complete for the practice activity -- Get social with github. Setup your account -- Go to https://github.com/elmsln/elmsln and star / watch / fork the repo -- Go to https://github.com/elmsln/haxcms and star / watch / fork the repo -- Go to https://github.com/elmsln/lrnwebcomponents and star / watch / fork the repo -- Go to this repo and star / watch / fork it -- https://github.com/btopro/lab2 -- From your copy of the repo, edit the README.md file (this file) and fill out the things below the FILL THIS OUT line -- Use the commit message in order to indicate what you changed -- Then issue a pull request back against this repo -- https://oer.hax.psu.edu/bto108/sites/ist402/labs/git will have the non-messed with directions as we'll screw up this repo to see how version control works during class +- [ ] Get social with github. Setup your account +- [ ] Go to https://github.com/elmsln/elmsln and star / watch / fork the repo +- [ ] Go to https://github.com/elmsln/haxcms and star / watch / fork the repo +- [ ] Go to https://github.com/elmsln/lrnwebcomponents and star / watch / fork the repo +- [ ] Go to this repo and star / watch / fork it -- https://github.com/btopro/lab2 +- [ ] From your copy of the repo, edit the README.md file (this file) and fill out the things below the FILL THIS OUT line +- [ ] Use the commit message in order to indicate what you changed +- [ ] Then issue a pull request back against this repo +- [ ] https://oer.hax.psu.edu/bto108/sites/ist402/labs/git will have the non-messed with directions as we'll screw up this repo to see how version control works during class # FILL THINGS OUT BELOW THIS LINE AND DO IT IN MARKDOWN From 6576fa50e3da525d6fd0ed7cd37a3de36efe9cc8 Mon Sep 17 00:00:00 2001 From: Eric Li Date: Wed, 4 Sep 2019 18:50:08 -0400 Subject: [PATCH 2/4] filled out all info below the line --- README.md | 41 ++++++++++++++++++++++++----------------- 1 file changed, 24 insertions(+), 17 deletions(-) diff --git a/README.md b/README.md index b2903ba..cb46b99 100644 --- a/README.md +++ b/README.md @@ -5,33 +5,40 @@ A repo to play with the common git operations in and learn how to get working wi - Desktop app (optional, very useful for development) https://desktop.github.com/ ## Steps to complete for the practice activity -- [ ] Get social with github. Setup your account -- [ ] Go to https://github.com/elmsln/elmsln and star / watch / fork the repo -- [ ] Go to https://github.com/elmsln/haxcms and star / watch / fork the repo -- [ ] Go to https://github.com/elmsln/lrnwebcomponents and star / watch / fork the repo -- [ ] Go to this repo and star / watch / fork it -- https://github.com/btopro/lab2 -- [ ] From your copy of the repo, edit the README.md file (this file) and fill out the things below the FILL THIS OUT line -- [ ] Use the commit message in order to indicate what you changed -- [ ] Then issue a pull request back against this repo -- [ ] https://oer.hax.psu.edu/bto108/sites/ist402/labs/git will have the non-messed with directions as we'll screw up this repo to see how version control works during class +- [x] Get social with github. Setup your account +- [x] Go to https://github.com/elmsln/elmsln and star / watch / fork the repo +- [x] Go to https://github.com/elmsln/haxcms and star / watch / fork the repo +- [x] Go to https://github.com/elmsln/lrnwebcomponents and star / watch / fork the repo +- [x] Go to this repo and star / watch / fork it -- https://github.com/btopro/lab2 +- [x] From your copy of the repo, edit the README.md file (this file) and fill out the things below the FILL THIS OUT line +- [x] Use the commit message in order to indicate what you changed +- [x] Then issue a pull request back against this repo +- [x] https://oer.hax.psu.edu/bto108/sites/ist402/labs/git will have the non-messed with directions as we'll screw up this repo to see how version control works during class # FILL THINGS OUT BELOW THIS LINE AND DO IT IN MARKDOWN ## Working definition of Git and what it's done for +> Git is a version control system for tracking changes in computer files and coordinating work on those files among multiple people. + +Long story short, Git is a collaborative platform, somewhat like the Google Doc (not working exactly the same way though), specifically designed for programmers. + +> It is primarily used for source code management in software development, but it can be used to keep track of changes in any set of files. + ## What do you think the top 3 reasons to use GitHub / GitLab are? -1. -2. -3. +1. Collaborate with other programmers within the team +2. Contribute to open source softwares +3. Safe for development as `git` keeps track of all file history ## What is a Pull Request? +Pull Request is a mechanism for you to take part in other people's code, usually a repo that you don't have push privilege to. It allows you to change some line(s) of codes in the repo, having discussion with the owner of the repo, and raising up potential issues etc. + ## Links to relevent Github / git tutorials - [Github](https://github.com/) -- Add a resource link here -- Add another resource link here - +- [CS50-Harvard](https://www.youtube.com/watch?v=MJUJ4wbFm_A) +- [Git Official Document](https://git-scm.com/docs/gittutorial) ### Change this image to be something else with different alt data -You can also do images like the one just below here using the ! -![Oh Spongebob](https://media.giphy.com/media/3oEjI4sFlp73fvEYgw/giphy.gif). + +![IT Crowd](https://media3.giphy.com/media/SZUnyVdIDAEQU/giphy.gif). \ No newline at end of file From d8e045af375f531c2f120047f89a8b6621782d4d Mon Sep 17 00:00:00 2001 From: Eric Li Date: Sun, 8 Sep 2019 15:59:24 -0400 Subject: [PATCH 3/4] update Reflection.md --- Reflection.md | 48 ++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 40 insertions(+), 8 deletions(-) diff --git a/Reflection.md b/Reflection.md index 01e5b18..7139ff7 100644 --- a/Reflection.md +++ b/Reflection.md @@ -1,9 +1,41 @@ # My Reflection / Blog -Use this file to submit your blog post to your github account / repo. In it, include some markdown to practice, especially a link to your video. -*Screencast submission* - [YouTube video by HAXcms core contributor Michael Potter](https://www.youtube.com/watch?v=5aPae031TxM&list=PLJQupiji7J5cGYiOflGYFwXSEoHMoowkP&index=17&t=0s) -Here's a reminder of how you do the link above as code. -```markdown -*Screencast submission* - [YouTube video by HAXcms core contributor Michael Potter](https://www.youtube.com/watch?v=5aPae031TxM&list=PLJQupiji7J5cGYiOflGYFwXSEoHMoowkP&index=17&t=0s) -``` - -Good luck! + +*Screencast submission* - [ZL's Lab2 Video](https://youtu.be/cMdzLb08Q1I) + +In this week's lab, we learned about version control, and to be more specific, how to use `git`, including `clone`, `push`, `pull` features, and how to make a *Pull Request*. This is a very useful tool since teamwork is a key element of software development at present and GitHub is the most popular platform where all these collaborations happen. + +It is also very interesting to see how Pull Request functions being very handy while a lot of people still don't know. I was trying to figure out such function during my summer internship and GitHub's own documentation on this was not clear at all (at least to me, blah). So I think it's probably a good idea for me to make a video on this as well and hopefully this can help someone who's in need to learn this and couldn't figure out from the documentation. + +And for the purpose of practicing `markdown`, refer below for the terminal commands I used in my video: + +
+> git clone "link to your repository" 
+
+ +
+> cd "directory location of your local repository" 
+
+ +
+> vim README.md
+
+ +
+> git status
+
+ +
+> git add .
+
+ +
+> git commit -m "commitment message"
+
+ +
+> git push
+
+ +
+> git pull
+
\ No newline at end of file From 8a76b245046ea6e82caf47a038e6b225cd0486c1 Mon Sep 17 00:00:00 2001 From: zlstravel <54683917+zlstravel@users.noreply.github.com> Date: Sun, 8 Sep 2019 16:00:15 -0400 Subject: [PATCH 4/4] Update Reflection.md --- Reflection.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Reflection.md b/Reflection.md index 7139ff7..3f3a6e4 100644 --- a/Reflection.md +++ b/Reflection.md @@ -9,11 +9,11 @@ It is also very interesting to see how Pull Request functions being very handy w And for the purpose of practicing `markdown`, refer below for the terminal commands I used in my video: 
-> git clone "link to your repository" 
+> git clone link to your repository 
 
-> cd "directory location of your local repository" 
+> cd directory location of your local repository 
 
@@ -38,4 +38,4 @@ And for the purpose of practicing `markdown`, refer below for the terminal comma
 
 
 > git pull
-

\ No newline at end of file
+