GIT Homework

Due.

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.

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 repository for group projects. You will sent your project name to the instructor so the project can be monitored.

GIT1.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.
  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 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. The team members wil create a master GitHub account for your team to share.
  2. The team members will install git on their personal computers. Instructions here.
  3. The team will create a new GitHub project (public) named for your project.
  4. Clone the project into your local git.
  5. One of the team members will push the initial copy of the notes and project proposal to git. It is suggest that you keep your documents in pure text form so that versioning will allow you to see changes.
  6. Each team member should make some minor changes to different files
  7. Each student should commit the changes: git commit
  8. Then do a pull to merge in any repository changes: git pull
  9. Then do a push to save changes to the repository: git push
  10. Check the files in your personal directory to see if everyones changes are there.
  11. Each student should make minor changes to different parts of the same file.
  12. Each one should do a commit, push, pull to to save and reconcile the differences as needed.
  13. Everyone should check the results
  14. Send a invitation to the project to the instructor (jimskon).
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

A 2-3 paragraph 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 could this lab be better?
A link to the github project

References

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

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng GIT1.png r1 manage 38.2 K 2017-12-03 - 05:25 JimSkon  
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r2 - 2018-02-01 - JimSkon
 
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