source from: http://spectrum.ieee.org/automaton/robotics/robotics-hardware/video-friday-6571524
It was inevitable, I guess: a fusion of ROS and… Wait for it… Minecraft. Now, using a Kinect sensor and ROS, you can import the a blocky 3D scan of the real world straight into Minecraft! YES! FINALLY!!!
Source from: https://help.github.com/articles/fork-a-repo
If you’ve found yourself on this page, we’re assuming you’re brand new to Git and GitHub. This guide will walk you through the basics and explain a little bit about how everything works along the way.
At some point you may find yourself wanting to contribute to someone else’s project, or would like to use someone’s project as the starting point for your own. This is known as “forking.” For this tutorial, we’ll be using the Spoon-Knife project.
To fork this project, click the “Fork” button.
You’ve successfully forked the Spoon-Knife repository, but so far it only exists on GitHub. To be able to work on the project, you will need to clone it to your local machine.
Run the following code:
git clone https://github.com/<em>username</em>/Spoon-Knife.git# Clones your fork of the repository into the current directory in terminal
When a repository is cloned, it has a default remote called origin that points to your fork on GitHub, not the original repository it was forked from. To keep track of the original repository, you need to add another remote named upstream:
cd Spoon-Knife# Changes the active directory in the prompt to the newly cloned "Spoon-Knife" directory git remote add upstream https://github.com/octocat/Spoon-Knife.git# Assigns the original repository to a remote called "upstream" git fetch upstream# Pulls in changes not present in your local repository, without modifying your files
You’ve successfully forked a repository, but get a load of these other cool things you can do:
Once you’ve made some commits to a forked repository and want to push it to your forked project, you do it the same way you would with a regular repository:
git push origin master# Pushes commits to your remote repository stored on GitHub
If the original repository you forked your project from gets updated, you can add those updates to your fork by running the following code:
git fetch upstream# Fetches any new changes from the original repository git merge upstream/master# Merges any changes fetched into your working files
Branching allows you to build new features or test out ideas without putting your main project at risk. In git, branch is a sort of bookmark that references the last commit made in the branch. This makes branches very small and easy to work with.
If you are hoping to contribute back to the original fork, you can send the original author a pull request.
When you fork a particularly popular repository, you may find yourself with a lot of unwanted updates about it. To unsubscribe from updates to the main repository, click the “Unwatch” button on the main repository.
At some point you may decide that you want to delete your fork. To delete a fork, just follow the same steps as you would to delete a regular repository.
Source from: https://help.github.com/articles/create-a-repo
If you’ve found yourself on this page, we’re assuming you’re brand new to Git and GitHub. This guide will walk you through the basics and explain a little bit about how everything works along the way.
Every time you make a commit with Git, it is stored in a repository (a.k.a. “repo”). To put your project up on GitHub, you’ll need to have a GitHub repository for it to live in.
Click New Repository.
Fill out the information on this page. When you’re done, click “Create Repository.”
Congratulations! You have successfully created your first repository!
While a README isn’t a required part of a GitHub repository, it is a very good idea to have one. READMEs are a great place to describe your project or add some documentation such as how to install or use your project. You might want to include contact information – if your project becomes popular people will want to help you out.
In the prompt, type the following code:
mkdir ~/Hello-World# Creates a directory for your project called "Hello-World" in your user directory cd ~/Hello-World# Changes the current working directory to your newly created directory git init# Sets up the necessary Git files # Initialized empty Git repository in /Users/<em>you</em>/Hello-World/.git/ touch README# Creates a file called "README" in your Hello-World directory
Open the new README file found in your Hello-World directory in a text editor and add the text “Hello World!” When you are finished, save and close the file.
Now that you have your README set up, it’s time to commit it. A commit is essentially a snapshot of all the files in your project at a particular point in time. In the prompt, type the following code:
git add README# Stages your README file, adding it to the list of files to be committed git commit -m 'first commit'# Commits your files, adding the message "first commit"
So far everything you’ve done has been in your local repository, meaning you still haven’t done anything on GitHub yet. To connect your local repository to your GitHub account, you will need to set a remote for your repository and push your commits to it:
git remote add origin https://github.com/<em>username</em>/Hello-World.git# Creates a remote named "origin" pointing at your GitHub repository git push origin master# Sends your commits in the "master" branch to GitHub
Now if you look at your repository on GitHub, you will see your README has been added to it.
