Github is a web service that does version control so that various programmers can work on the same code and still keep up to date as changes are being made.

XP Template for LRNG entryEdit


  • XP/Github



edit me

Resources (optinal)Edit

Are there any resources that would help learners complete this XP?

  • http://
  • Enter Resource Title
    • Repeat if desired.

Submission RequirementsEdit

Describe the evidence a learner must submit to complete this XP.

edit me

Learning DetailsEdit

Set the Interest, Age, Participation, and Duration of your XP.

  • Interest
  • Age Appropriateness
  • Estimated Duration
    • hr
    • min


  1. Read about Github on Wikipedia, Wikipedia:Github.
  2. Get your own account on Github with a username and log in.
  3. Save your new username and password in your safe.
  4. Post your new username onto your wiki home page. Do not post the password.
  5. Take the tour on Github.
  6. Watch the following five videos:
    1. Github Tutorial For Beginners - Github Basics for Mac or Windows & Source Control Basics-1

      Github Tutorial For Beginners - Github Basics for Mac or Windows & Source Control Basics-1

  7. Review these terms on this wiki and make sure you understand them.
    1. Repository, Git Pull, Github Merge conflict, Escape:WQ,
  8. Write a harmless letter and put it into your Github directory.
  9. Use another computer to go get that document. Make a change. Save the changes.
  10. Peek at 5 resumes on Github.
  11. Explore 5 projects on Github including:
  12. Write a simple LiveCode project and upload it to Github.
  13. Get a LiveCode project from Github from another person.


Social tasksEdit


Hello World on GitHubEdit

  • The Hello World project is a time-honored tradition in computer programming. It is a simple exercise that gets you started in 10 to 30 minutes.

GitHub is a code hosting platform for version control and collaboration. GitHub is a popular way to create and review code letting people work together on projects from anywhere. No coding is necessary. To complete this tutorial, you need a account and Internet access. You don’t need to know how to code, use the command line, or install Git (the version control software GitHub is built on).

Learn how to:Edit

  1. Create and use a repository.
  2. Start and manage a new branch.
  3. Make changes to a file and push them to GitHub as commits.
  4. Open and merge a pull request.

This EXP tutorial teaches GitHub essentials like repositories, branches, commits, and pull requests. You’ll create your own Hello World repository and learn GitHub’s pull request workflow, .

Step 1. Create a RepositoryEdit

Step 2. Create a BranchEdit

Branching is the way to work on different versions of a repository at one time.

By default your repository has one branch named master which is considered to be the definitive branch. We use branches to experiment and make edits before committing them to master.

When you create a branch off the master branch, you’re making a copy, or snapshot, of master as it was at that point in time. If someone else made changes to the master branch while you were working on your branch, you could pull in those updates.

Step 3. Make and commit changesEdit

On GitHub, saved changes are called commits. Each commit has an associated commit message, which is a description explaining why a particular change was made. Commit messages capture the history of your changes, so other contributors can understand what you’ve done and why.

Step 4. Open a Pull RequestEdit

Pull Requests are the heart of collaboration on GitHub. When you open a pull request, you’re proposing your changes and requesting that someone review and pull in your contribution and merge them into their branch. Pull requests show diffs, or differences, of the content from both branches. The changes, additions, and subtractions are shown in green and red.

As soon as you make a commit, you can open a pull request and start a discussion, even before the code is finished.

By using GitHub’s @mention system in your pull request message, you can ask for feedback from specific people or teams, whether they’re down the hall or 10 time zones away.

You can even open pull requests in your own repository and merge them yourself. It’s a great way to learn the GitHub Flow before working on larger projects.

Step 5. Merge your Pull RequestEdit

Bring your changes together – merging your readme-edits branch into the master branch.

Here’s what you accomplish in this tutorial:Edit

  1. Created an open source repository
  2. Started and managed a new branch
  3. Changed a file and committed those changes to GitHub
  4. Opened and merged a Pull Request
  5. Take a look at your GitHub profile and you’ll see your new contribution squares!