Difference: SDGitHW (1 vs. 14)

Revision 142018-10-10 - JimSkon

Line: 1 to 1
 
META TOPICPARENT name="Spring2017"

GIT Homework

Changed:
<
<
Due February 28.
>
>
Due Oct 17.
  Moodle
Goal

Revision 132018-02-27 - JimSkon

Line: 1 to 1
 
META TOPICPARENT name="Spring2017"

GIT Homework

Changed:
<
<
Due February 21.
>
>
Due February 28.
  Moodle
Goal
Line: 37 to 37
 
    • On github click "Start a project", enter in the name.
    • Go to the project on cslab.
    • Delete any old project git files (in case you started from my nameserver project) using "rm -rf .git".
Changed:
<
<
    • Go back to the newly created project on github. You will see a set of commands under the heading "…or create a new repository on the command line" that look somthing like:
      echo "# exampleproject" >> README.md
      git init
      git add README.md
      git commit -m "first commit"
      git remote add origin https://github.com/expertlearningsystems/exampleproject.git
      git push -u origin master
      Copy and paste this into the command line while in the project 1 directory. You will need to log into gih hub.

>
>
    • Go back to the newly created project on github. You will see a set of commands under the heading "…or create a new repository on the command line" that look somthing like:
      echo "# exampleproject" >> README.md git init git add README.md git commit -m "first commit" git remote add origin https://github.com/expertlearningsystems/exampleproject.git git push -u origin master
      Copy and paste this into the command line while in the project 1 directory. You will need to log into gih hub.

 
    • If you get a message "Please tell who you are", copy the commands and put in your username and email.
    • Do a "make clean" to remove object files.
    • Do a "git add *" to add everything to the project

Revision 122018-02-21 - JimSkon

Line: 1 to 1
 
META TOPICPARENT name="Spring2017"

GIT Homework

Due February 21.
Line: 31 to 31
 You will work with your team to create a GIT repository on the server using project 3. Then set it up at GitHub. Finally your other teammates and you will experiment with using this GitHub repositroy from several accounts.

Steps

Changed:
<
<
  1. All of the team members wil create GitHub accounts.
  2. One of the team members will create a new GitHub project (public) called nameserver. The other members will be invited to the project.
>
>
  1. All of the team members will create GitHub accounts.
  2. One of the team members will create a new GitHub project (public) in their avcount called ShakeProject.
  3. The same team member will turn their Project 1 into a Git project. This will push the project to the GitHub repository.
    • On github click "Start a project", enter in the name.
    • Go to the project on cslab.
    • Delete any old project git files (in case you started from my nameserver project) using "rm -rf .git".
    • Go back to the newly created project on github. You will see a set of commands under the heading "…or create a new repository on the command line" that look somthing like:
      echo "# exampleproject" >> README.md
      git init
      git add README.md
      git commit -m "first commit"
      git remote add origin https://github.com/expertlearningsystems/exampleproject.git
      git push -u origin master
      Copy and paste this into the command line while in the project 1 directory. You will need to log into gih hub.

    • If you get a message "Please tell who you are", copy the commands and put in your username and email.
    • Do a "make clean" to remove object files.
    • Do a "git add *" to add everything to the project
    • Do a "git commit *" to commit to github. You will need to type in a comment into the editor, and hit control-o, return, control-x.
    • Do a "git push" to push the files to github. you will need to enter your gitghub credentials.
  4. The other members will be invited to the project. To invite click settings, and then collaborators. Enter in member names to send an invitation.
 
  1. The other teams members accept membership
Changed:
<
<
  1. One of the team members will turn their Project 2 into a Git project. Instructions Here. Example Here. This will push the project to the GitHub repository.
  2. The other students will create a new directory, go into the directory, and create a new empty git repository, and clone the project 2 into their directory. Instructions here. Example here.
>
>
  1. The other students will clone the new github into their directory. They will enter "git clone github-project-url"
 
  1. Each team member should make some minor changes to different files (perhaps in the code comments).
Changed:
<
<
  1. Each student should commit the changes: git commit
>
>
  1. Each student should commit the changes for the files changed: git commit _file_
 
  1. Then do a pull to merge in any repository changes: git pull
  2. Then do a push to save changes to the repository: git push
  3. Check the files in your personal directory to see if everyones changes are there.
Line: 50 to 65
 
  1. You can now use GitHub for you editor instead of Notepad++ or textwranger if you choose.

Turn in

Changed:
<
<
A 2-3 lab report answering:
>
>
A short lab report answering:
 
  1. What are the purposes of Git?
  2. What is github versus git?
  3. What problems did you experience in this lab?

Revision 112018-02-16 - JimSkon

Line: 1 to 1
 
META TOPICPARENT name="Spring2017"

GIT Homework

Changed:
<
<
Due February 15.
>
>
Due February 21.
 
Changed:
<
<
Moodle
>
>
Moodle
 
Goal

For this classes we will use GIT to track our projects on the GitHub server. GitHub is free for public processes, but costs money for (about $7.00 a month) for private projects. It is assumed your projects will be public, but you are free to make them private is you wish to. However, the instructor must have access to all class related projects for grading purposes.

Line: 56 to 56
 
  1. What problems did you experience in this lab?
  2. How you resolved the problems given above?
  3. how could this lab be better?
Added:
>
>
  1. A link to your github account
 

References

Review the following as needed. Remember you can ignore things relating to INSTALLING and REMOTES.

Revision 102017-11-03 - JimSkon

Line: 1 to 1
 
META TOPICPARENT name="Spring2017"

GIT Homework

Due February 15.
Line: 28 to 28
 
  1. Indiviiduals do a push to update master (git push)

Goal

Changed:
<
<
You will work with your team to create a GIT repository on the server using project 2. Then set it up at GitHub. Finally your other teammates and you will experiment with using this GitHub repositroy from several accounts.
>
>
You will work with your team to create a GIT repository on the server using project 3. Then set it up at GitHub. Finally your other teammates and you will experiment with using this GitHub repositroy from several accounts.
 

Steps

  1. All of the team members wil create GitHub accounts.
  2. One of the team members will create a new GitHub project (public) called nameserver. The other members will be invited to the project.
Changed:
<
<
  1. The other teams memeber accept membership
>
>
  1. The other teams members accept membership
 
  1. One of the team members will turn their Project 2 into a Git project. Instructions Here. Example Here. This will push the project to the GitHub repository.
  2. The other students will create a new directory, go into the directory, and create a new empty git repository, and clone the project 2 into their directory. Instructions here. Example here.
  3. Each team member should make some minor changes to different files (perhaps in the code comments).

Revision 92017-02-22 - JimSkon

Line: 1 to 1
 
META TOPICPARENT name="Spring2017"

GIT Homework

Due February 15.
Line: 11 to 11
  Git is typically used for a group to synchronize their activities. to do this there is a common repository server that everyone pushes to and pulls from, and sometimes merges with. We will be using GitHub as our repository. GitHub is an online repository that alows groups of people to work on a project together, allowing them to work on and synchronize their work. It also keeps a complete history of ALL versions of every file in the project. In this class all groups are required to create an use a repository for group projects. You will sent your project name to the instructor so the project can be monitored.
Changed:
<
<
You will manage the code state with "commit", "push", "pull", "clone", and "fetch" operation.
>
>
GIT1.png
 
Changed:
<
<
GIT.png
>
>
You will manage the code state with "commit", "push", "pull", "clone", and "fetch" operation.
  The process works as follows.
  1. A project is created on Github.
Line: 63 to 63
 
Changed:
<
<

>
>
  • GIT1.png:
 
Changed:
<
<
META FILEATTACHMENT attachment="GIT.png" attr="" comment="" date="1487007870" name="GIT.png" path="GIT.png" size="39029" user="JimSkon" version="2"
>
>
META FILEATTACHMENT attachment="GIT1.png" attr="" comment="" date="1487761409" name="GIT1.png" path="GIT1.png" size="39116" user="JimSkon" version="1"

Revision 82017-02-19 - JimSkon

Line: 1 to 1
 
META TOPICPARENT name="Spring2017"

GIT Homework

Due February 15.
Line: 55 to 55
 
  1. What is github versus git?
  2. What problems did you experience in this lab?
  3. How you resolved the problems given above?
Changed:
<
<
  1. how gould this lab be better?
>
>
  1. how could this lab be better?
 

References

Review the following as needed. Remember you can ignore things relating to INSTALLING and REMOTES.

Line: 65 to 65
 

Deleted:
<
<

 
META FILEATTACHMENT attachment="GIT.png" attr="" comment="" date="1487007870" name="GIT.png" path="GIT.png" size="39029" user="JimSkon" version="2"

Revision 72017-02-13 - JimSkon

Line: 1 to 1
 
META TOPICPARENT name="Spring2017"

GIT Homework

Due February 15.
Line: 13 to 13
  You will manage the code state with "commit", "push", "pull", "clone", and "fetch" operation.
Added:
>
>
GIT.png

The process works as follows.

  1. A project is created on Github.
  2. Init a git repository in a project (git init)
  3. Add the files to the local repository (git add .)
  4. Commit the files to the new repository (git commit)
  5. Other gets the code into their private repository and code base (git clone)
  6. Team members work on code and test locally. (use textwrangler and notepad++, make, and test)
  7. Individuals commit work (git commit)
  8. Individuals pull to get any changes in main repository (git pull)
  9. Individuals may have to merge changes in main repository with local changes.
  10. Indiviiduals do a push to update master (git push)

Goal

 You will work with your team to create a GIT repository on the server using project 2. Then set it up at GitHub. Finally your other teammates and you will experiment with using this GitHub repositroy from several accounts.

Steps

Line: 49 to 64
 

\ No newline at end of file
Added:
>
>

META FILEATTACHMENT attachment="GIT.png" attr="" comment="" date="1487007870" name="GIT.png" path="GIT.png" size="39029" user="JimSkon" version="2"

Revision 62017-02-12 - JimSkon

Line: 1 to 1
 
META TOPICPARENT name="Spring2017"

GIT Homework

Changed:
<
<
Due February 17.
>
>
Due February 15.
  Moodle
Goal

Revision 52017-02-11 - JimSkon

Line: 1 to 1
 
META TOPICPARENT name="Spring2017"

GIT Homework

Changed:
<
<
Due February 13.
>
>
Due February 17.
  Moodle
Goal

Revision 42017-02-09 - JimSkon

Line: 1 to 1
 
META TOPICPARENT name="Spring2017"

GIT Homework

Due February 13.
Line: 29 to 29
 
  1. Each student should make minor changes to different parts of the same file.
  2. Each one should do a commit, push, pull to to save and reconcile the differences as needed.
  3. Everyone should check the results
Changed:
<
<
>
>
Working from GitHub
  1. Go to the github.com site. Log in. Notice how you can edit the code, and commit
  2. Click the history button on a file that has changes. Look at the history in Unified nd Split modes.
  3. You can now use GitHub for you editor instead of Notepad++ or textwranger if you choose.
 

Turn in

Changed:
<
<
A 2-3 paragraph lab report explaining:
  1. What you learned
  2. What problems you experienced
  3. How you resolved those problems.
>
>
A 2-3 lab report answering:
  1. What are the purposes of Git?
  2. What is github versus git?
  3. What problems did you experience in this lab?
  4. How you resolved the problems given above?
  5. how gould this lab be better?
 

References

Review the following as needed. Remember you can ignore things relating to INSTALLING and REMOTES.

Revision 32017-02-09 - JimSkon

Line: 1 to 1
 
META TOPICPARENT name="Spring2017"

GIT Homework

Due February 13.
Line: 11 to 11
  Git is typically used for a group to synchronize their activities. to do this there is a common repository server that everyone pushes to and pulls from, and sometimes merges with. We will be using GitHub as our repository. GitHub is an online repository that alows groups of people to work on a project together, allowing them to work on and synchronize their work. It also keeps a complete history of ALL versions of every file in the project. In this class all groups are required to create an use a repository for group projects. You will sent your project name to the instructor so the project can be monitored.
Changed:
<
<
You will manage the code state with "push", "pull", "clone", and "fetch" operation.
>
>
You will manage the code state with "commit", "push", "pull", "clone", and "fetch" operation.
  You will work with your team to create a GIT repository on the server using project 2. Then set it up at GitHub. Finally your other teammates and you will experiment with using this GitHub repositroy from several accounts.

Steps

Line: 21 to 21
 
  1. The other teams memeber accept membership
  2. One of the team members will turn their Project 2 into a Git project. Instructions Here. Example Here. This will push the project to the GitHub repository.
  3. The other students will create a new directory, go into the directory, and create a new empty git repository, and clone the project 2 into their directory. Instructions here. Example here.
Changed:
<
<
  1. Each team meber should make some minor changes to different files (perhaps in the code comments)
  2. Each student should push the results to github.
  3. Each student should push to see the changes.
>
>
  1. Each team member should make some minor changes to different files (perhaps in the code comments).
  2. Each student should commit the changes: git commit
  3. Then do a pull to merge in any repository changes: git pull
  4. Then do a push to save changes to the repository: git push
  5. Check the files in your personal directory to see if everyones changes are there.
 
  1. Each student should make minor changes to different parts of the same file.
Changed:
<
<
  1. Each should try to push, and reconcile the differences as needed.
  2. Everyone should pull and see the results
>
>
  1. Each one should do a commit, push, pull to to save and reconcile the differences as needed.
  2. Everyone should check the results
 

Turn in

Revision 22017-02-08 - JimSkon

Line: 1 to 1
 
META TOPICPARENT name="Spring2017"

GIT Homework

Added:
>
>
Due February 13.
 
Changed:
<
<
Due February 13.

Goal

>
>
Moodle
Goal
 
Changed:
<
<
For this classes we will use GIT to track our projects on the GitHub server. GitHub is free for public processes, but costs money for (about $7.00 a month) for private projects. It is assumed your projects will be public, but you are free to make them private is you wish to. However, the instructor must have access to all class related projects for grading purrposes.
>
>
For this classes we will use GIT to track our projects on the GitHub server. GitHub is free for public processes, but costs money for (about $7.00 a month) for private projects. It is assumed your projects will be public, but you are free to make them private is you wish to. However, the instructor must have access to all class related projects for grading purposes.
 

Overview

Git is typically used for a group to synchronize their activities. to do this there is a common repository server that everyone pushes to and pulls from, and sometimes merges with. We will be using GitHub as our repository. GitHub is an online repository that alows groups of people to work on a project together, allowing them to work on and synchronize their work. It also keeps a complete history of ALL versions of every file in the project. In this class all groups are required to create an use a repositoryfor group projects. You will sent your project name to the instructor so the project can be monitored.

Line: 18 to 19
 
  1. All of the team members wil create GitHub accounts.
  2. One of the team members will create a new GitHub project (public) called nameserver. The other members will be invited to the project.
  3. The other teams memeber accept membership
Changed:
<
<
  1. One of the team members will turn their Project 2 into a Git project. Instructions Here. Example Here. This will push the project to the GitHub repositroy.
>
>
  1. One of the team members will turn their Project 2 into a Git project. Instructions Here. Example Here. This will push the project to the GitHub repository.
 
  1. The other students will create a new directory, go into the directory, and create a new empty git repository, and clone the project 2 into their directory. Instructions here. Example here.
Added:
>
>
  1. Each team meber should make some minor changes to different files (perhaps in the code comments)
  2. Each student should push the results to github.
  3. Each student should push to see the changes.
  4. Each student should make minor changes to different parts of the same file.
  5. Each should try to push, and reconcile the differences as needed.
  6. Everyone should pull and see the results

Turn in

A 2-3 paragraph lab report explaining: 1 What you learned 1 What problems you experienced 1 How you resolved those problems.

 

References

Review the following as needed. Remember you can ignore things relating to INSTALLING and REMOTES.

Line: 29 to 44
 

Deleted:
<
<
For all the steps below make a word processing document that chows and explains each command you had to use.

  1. Initialize and set up a local Git.
  2. Add your project code to the local Git as a new project (you will have others later)
  3. Show how to commit new changes.
  4. Show how to revert back to the previous commit after making changes. What is this useful for?
  5. Show how to compare two different of the same file.
  6. Show how to bring back an older version of a file without reverting.
  7. Show how to add and remove files from a Git repository.
  8. Show how to exclude certain files from being tracked by Git. What is this is important.
  9. Turn is all in on Moodle.

Revision 12017-02-08 - JimSkon

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="Spring2017"

GIT Homework

Due February 13.

Goal

For this classes we will use GIT to track our projects on the GitHub server. GitHub is free for public processes, but costs money for (about $7.00 a month) for private projects. It is assumed your projects will be public, but you are free to make them private is you wish to. However, the instructor must have access to all class related projects for grading purrposes.

Overview

Git is typically used for a group to synchronize their activities. to do this there is a common repository server that everyone pushes to and pulls from, and sometimes merges with. We will be using GitHub as our repository. GitHub is an online repository that alows groups of people to work on a project together, allowing them to work on and synchronize their work. It also keeps a complete history of ALL versions of every file in the project. In this class all groups are required to create an use a repositoryfor group projects. You will sent your project name to the instructor so the project can be monitored.

You will manage the code state with "push", "pull", "clone", and "fetch" operation.

You will work with your team to create a GIT repository on the server using project 2. Then set it up at GitHub. Finally your other teammates and you will experiment with using this GitHub repositroy from several accounts.

Steps

  1. All of the team members wil create GitHub accounts.
  2. One of the team members will create a new GitHub project (public) called nameserver. The other members will be invited to the project.
  3. The other teams memeber accept membership
  4. One of the team members will turn their Project 2 into a Git project. Instructions Here. Example Here. This will push the project to the GitHub repositroy.
  5. The other students will create a new directory, go into the directory, and create a new empty git repository, and clone the project 2 into their directory. Instructions here. Example here.

References

Review the following as needed. Remember you can ignore things relating to INSTALLING and REMOTES.

For all the steps below make a word processing document that chows and explains each command you had to use.

  1. Initialize and set up a local Git.
  2. Add your project code to the local Git as a new project (you will have others later)
  3. Show how to commit new changes.
  4. Show how to revert back to the previous commit after making changes. What is this useful for?
  5. Show how to compare two different of the same file.
  6. Show how to bring back an older version of a file without reverting.
  7. Show how to add and remove files from a Git repository.
  8. Show how to exclude certain files from being tracked by Git. What is this is important.
  9. Turn is all in on Moodle.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback