mirror/pcottle.learnGitBranching
1
0
Fork 0
mirror of https://github.com/pcottle/learnGitBranching.git synced 2025-06-26 16:08:34 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Typo

Browse source
This commit is contained in:
Crisci, Fabio | Piuccio | TRVDD 2013-10-15 08:42:05 +09:00
parent f543fa4485
commit b24f443266
3 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

2
src/levels/remote/clone.js
View file

@ -16,7 +16,7 @@ exports.level = {
"markdowns": [ "markdowns": [
"## Git Remotes", "## Git Remotes",
"", "",
"Remote repositories aren't actually that complicated. In today's world of cloud computing it's easy to think that there's a lot of magic behind git remotes, but they are actually just copies of your repositoy on another computer. You can typically talk to this other computer through the internet, which allows you to transfer commits back and forth.", "Remote repositories aren't actually that complicated. In today's world of cloud computing it's easy to think that there's a lot of magic behind git remotes, but they are actually just copies of your repository on another computer. You can typically talk to this other computer through the Internet, which allows you to transfer commits back and forth.",
"", "",
"That being said, remote repositories have a bunch of great properties:", "That being said, remote repositories have a bunch of great properties:",
"", "",

4
src/levels/remote/fetch.js
View file

@ -21,7 +21,7 @@ exports.level = {
"", "",
"In this lesson we will learn how to fetch data _from_ a remote repository -- the command for this is conveniently named `git fetch`.", "In this lesson we will learn how to fetch data _from_ a remote repository -- the command for this is conveniently named `git fetch`.",
"", "",
"You'll notice that as we update our representation of the remote repository, our _remote_ branches will update to reflect that new repsentation. This ties into the previous lesson on remote branches" "You'll notice that as we update our representation of the remote repository, our _remote_ branches will update to reflect that new representation. This ties into the previous lesson on remote branches"
] ]
} }
}, },
@ -53,7 +53,7 @@ exports.level = {
"", "",
"If you remember from the previous lesson, we said that remote branches reflect the state of the remote repositories _since_ you last talked to those remotes. `git fetch` is the way you talk to these remotes! Hopefully the connection between remote branches and `git fetch` is apparent now", "If you remember from the previous lesson, we said that remote branches reflect the state of the remote repositories _since_ you last talked to those remotes. `git fetch` is the way you talk to these remotes! Hopefully the connection between remote branches and `git fetch` is apparent now",
"", "",
"`git fetch` usually talks to the remote repository through the internet (via a protocol like `http://` or `git://`).", "`git fetch` usually talks to the remote repository through the Internet (via a protocol like `http://` or `git://`).",
"" ""
] ]
} }

2
src/levels/remote/fetchRebase.js
View file

@ -143,7 +143,7 @@ exports.level = {
"", "",
"In order to solve this level, take the following steps:", "In order to solve this level, take the following steps:",
"", "",
"* Clone your repro", "* Clone your repo",
"* Fake some teamwork (1 commit)", "* Fake some teamwork (1 commit)",
"* Commit some work yourself (1 commit)", "* Commit some work yourself (1 commit)",
"* Publish your work via *rebasing*" "* Publish your work via *rebasing*"