Skip to main content

Hello World GitHub!

Hello World

The Hello World project is a time-honored tradition in computer programming. It is a simple exercise that gets you started when learning something new. Let’s get started with GitHub!
GitHub is a platform for hosting and collaborating on projects. You don’t have to worry about losing data on your hard drive or managing a project across multiple computers — sync from anywhere. Most importantly, GitHub is a collaborative and asynchronous workflow for building software better, together.
This guide walks you through the GitHub Essentials: RepositoriesBranches,CommitsIssues and Pull Requests.
With these skills, you’ll go far. And with this hello-world repository you’ll have a place to store ideas (aka future repositories, like jlord/hello-world), resources or other general notes, even discuss things with others (like holman/feedback).

Install & Code Free Zone

We’re going to complete the tasks in this tutorial using GitHub.com, so you don’t have to know the command line or even install Git (which is the change-tracking software GitHub is built on). You don’t even need to know how to code. You will, however, need a GitHub account, so sign up if you don’t have one!
Tip: Open this guide in a separate browser window (or tab) so you can see it while you complete the steps in the tutorial.

Create a Repository

repository is the basic unit of GitHub, most commonly a single project. Repositories can contain folders and files, including images – anything your project needs. Because we recommend including a README, or a file describing the project, in every repository, GitHub makes it easy to add one at the same time you create your new repository. It also offers other common options such as a license file, but we can skip that for now.

To create a new repository

  1. Click the  icon next to your username, top-right.
  2. Name your repository hello-world.
  3. Write a short description.
  4. Select Initialize this repository with a README.
new-repo-form
Click Create repository. Boom, repository! :boom:

Open an Issue

An Issue is a note on a repository about something that needs attention. It could be a bug, a feature request, a question or lots of other things. On GitHub you can label, search and assign Issues, making managing an active project easier.
You’ve got a repository now, but it’s pretty bare. It could use a README with more information in it so that people know what is going on. Open an Issue!

Open an Issue for README edits

  1. Click the  Issues tab from the sidebar.
  2. Click New Issue.
  3. Give your Issue a title and description.
issue
Click Submit new Issue when you’re done. Now this issue has a permanent home (URL) that you can reference even after it is closed.
Next, work towards editing your README and closing this issue.

Create a Branch

Branching is the way to work on different parts of a repository at one time.
When you create a repository, by default it has one branch with the namemaster. You could keep working on this branch and have only one, that’s fine. But if you have another feature or idea you want to work on, you can create another branch, starting from master, so that you can leave master in its working state.
When you create a branch, you’re making a copy of the original branch as it was at that point in time (like a photo snapshot). If the original branch changes while you’re working on your new branch, no worries, you can always pull in those updates.
a branch
You may have, at some point in your life, saved different versions of a file like, “story.txt”, “story-joe-edit.txt”, “story-sue-edit.txt”. Branches accomplish the same goals but are easier to manage on GitHub repositories.
At GitHub, our developers, writers, and designers use branches for keeping bug fixes and feature work separate from our master (production) branch. When a feature or fix is ready, the branch is merged into master.

To create a new branch

  1. Go to your new repository hello-world.
  2. Click the drop down at the top of the file list that says branch: master.
  3. Type a branch name, readme-edits, into the new branch text box.
  4. Select the blue Create branch box or hit “Enter” on your keyboard.
branch gif
Now you have two branches, master and readme-edits. They look exactly the same, but not for long! Next we’ll add our changes to the new branch.

Make a commit

On GitHub, saved changes are called commits. Commits are pretty glorious, because a bunch of them together read like the history of your project.
Each commit has an associated commit message, which is a description explaining why a particular change was made. Thanks to these messages, you and others can read through commits and understand what you’ve done and why.
You should still be on the code view for your readme-edits branch, now make some changes!

To commit changes

  1. Click the README file.
  2. Click the pencil icon in the upper right corner of the file view to edit.
  3. In the editor, write some text, tell a bit about yourself.
  4. Write a commit message that describes your changes.
commit
Click Commit changes. Now these changes have been made to the README file on your readme-edits branch and now this branch contains different content and commits than master (as it should!).

Open a Pull Request

Pull Requests are the heart of collaboration on GitHub. When you make a pull request, you’re proposing your changes and requesting that someone pull in your contribution - aka merge them into their branch. GitHub’s Pull Request feature allows you to compare the content on two branches. The changes, additions and subtractions, are shown in green and red and called diffs(differences).
As soon as you make a change, you can open a Pull Request. People use Pull Requests to start a discussion about commits (code review) even before the code is finished. This way you can get feedback as you go or help when you’re stuck.
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, as we’re doing here, a Pull Request in your own repository and merge it yourself. It’s a great way to learn to process before working on larger projects.

Create a Pull Request for changes to the README

Click on the image for a larger version
StepScreenshot
Click the  Pull Request icon on the sidebar, then from the Pull Request page, click the green New pull request button.create pr
Select the branch you made,readme-edits, to compare withmaster (the original).branch
Look over your changes in the diffs on the Compare page, make sure they’re what you want to submit.diff
When you’re satisfied that these are the changes you want to submit, click the big green Create Pull Request button.create-pull
Give your pull request a title and since it relates directly to an open issue, include “fixes #” and the issue number in the title. Write a brief description of your changes.pr-form
When you’re done with your message, click Create pull request!

Tip: You can use emoji and drag and drop images and gifs onto comments and Pull Requests.

Merge your Pull Request

It’s time to bring your changes together – merge your readme-edits branch into the master branch.
  1. Click the green button to merge the changes into master.
  2. Click Confirm merge.
  3. Go ahead and delete the branch, since its changes have been incorporated, with the Delete branch button in the purple box.
mergedelete
If you revisit the issue you opened, it’s now closed! Because you included “fixes #1” in your Pull Request title, GitHub took care of closing that issue when the Pull Request was merged!

Celebrate!

You’ve learned to make a pull request on GitHub! :tada: :octocat: :zap:
For your humblebrag, here are the things you accomplished in this tutorial: created a repository, branch, issue, and pull request, then merged a pull request! Show off your new contribution squares!
If you want to learn more about the power of pull requests, we recommend reading the GitHub Flow Guide. You might also visit GitHub Explore and get involved in an Open Source project :octocat:

Tip: Check out our other Guides and YouTube Channel for more GitHub how-tos.

Popular posts from this blog

Hidden Wiki

Welcome to The Hidden WikiNew hidden wiki url 2015 http://zqktlwi4fecvo6ri.onion Add it to bookmarks and spread it!!!
Editor's picks Bored? Pick a random page from the article index and replace one of these slots with it.
The Matrix - Very nice to read. How to Exit the Matrix - Learn how to Protect yourself and your rights, online and off. Verifying PGP signatures - A short and simple how-to guide. In Praise Of Hawala - Anonymous informal value transfer system. Volunteer Here are five different things that you can help us out with.
Plunder other hidden service lists for links and place them here! File the SnapBBSIndex links wherever they go. Set external links to HTTPS where available, good certificate, and same content. Care to start recording onionland's history? Check out Onionland's Museum Perform Dead Services Duties. Introduction PointsAhmia.fi - Clearnet search engine for Tor Hidden Services (allows you to add new sites to its database). DuckDuckGo - A Hidden S…

[SOLVED] IDM WAS REGISTERED WITH A FAKE SERIAL NUMBER

[SOLVED] IDM WAS REGISTERED WITH A FAKE SERIAL NUMBER
Good News [May 08, 2015]: IDM developers got smarter, but the crackers are always a step ahead. Follow this article and send an email to uglyduckblog@gmail.com if you are desperate. I can NOT post any crack here for legal reasons. Happy Downloading with IDM. ;) *********** first tip is to use latest crack for idm from  onhax.net idm universal web crack and make sure u are using all latest vers I am sure many of us are too much dependent on Internet Download Manager a.k.a. IDM. The main reason didn’t permanently switch to linux was IDM. I mainly use it for batch downloading and download streaming videos. Till yesterday, IDM was working fine with me (of course with fake serial numbers, keygen, crack, patch etc. which could be found with little effort). But few days ago, with the latest update version 6.18 build 7 (released on Nov 09, 2013) Internet Download Manager was literally had a breakthrough and crushed all the serial numbers, …

Mouse, touchpad, and keyboard problems in Windows

Mouse, touchpad, and keyboard problems in Windows Introduction This tutorial is designed to help you identify and fix common mouse, touchpad, and keyboard problems in Windows. It doesn't cover device problems related to specific programs. Mouse, touchpad, and keyboard problems can have a number of causes: Cables that aren't connected properly Incorrect device settings Missing updates Corrupted or incompatible drivers Hardware problems Check hardware Many mouse, touchpad, and keyboard problems are caused by hardware that isn't set up properly. Here's some information about how to check your device, make sure cables are connected properly, make sure the hardware has power, and check the settings. Make sure cables are connected properly Check that all cables are plugged in to the correct locations. This can include mouse and keyboard, PS2 and USB cables, and, in some cases, external USB touchpad cables. Disconnect USB cables and wait for a short time for the device drive…