mirror of
https://github.com/pcottle/learnGitBranching.git
synced 2025-06-25 23:48:34 +02:00
rebuild for fb page post
This commit is contained in:
Peter Cottle
parent
e053e4003a
commit
00a843754e
6 changed files with 215 additions and 211 deletions
282
build/bundle.js
282
build/bundle.js
|
|
@ -16494,6 +16494,7 @@ function getMockVisualization() {
|
|||
var treeString = options.treeString;
|
||||
|
||||
var headless = new HeadlessGit();
|
||||
headless.gitEngine.loadTreeFromString(treeString);
|
||||
return {
|
||||
customEvents: {
|
||||
on: function(key, cb, context) {
|
||||
|
|
@ -23046,7 +23047,7 @@ require.define("/src/levels/remote/clone.js",function(require,module,exports,__d
|
|||
"Up until this point, Learn Git Branching has focused on teaching the basics of _local_ repository work (branching, merging, rebasing, etc). However now that we want to learn about remote repository work, we need a command to set up the environment for those lessons. `git clone` will be that command",
|
||||
"",
|
||||
"Technically, `git clone` in the real world is the command you'll use to create _local_ copies of remote repositories (from github for example). We use this command a bit differently in Learn Git Branching though -- `git clone` actually makes a remote repository out of your local one. Sure it's technically the opposite meaning of the real command, but it helps build the connection between cloning and remote repository work, so let's just run with it for now.",
|
||||
"",
|
||||
""
|
||||
]
|
||||
}
|
||||
},
|
||||
|
|
@ -23091,75 +23092,75 @@ require.define("/src/levels/remote/fetch.js",function(require,module,exports,__d
|
|||
"en_US": "just run git fetch!"
|
||||
},
|
||||
"startDialog": {
|
||||
"en_US": {
|
||||
"childViews": [
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"## Git Fetch",
|
||||
"",
|
||||
"Working with git remotes really just boils down to transferring data _to_ and _from_ other repositories. As long as we can send commits back and forth, we can share any type of update that is tracked by git (and thus share work, new files, new ideas, love letters, etc etc).",
|
||||
"",
|
||||
"In this lesson we will learn how to fetch data _from_ a remote repository -- the command for this is conveniently named `git fetch`."
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "GitDemonstrationView",
|
||||
"options": {
|
||||
"beforeMarkdowns": [
|
||||
"Before getting into the details of `git fetch`, let's see it in action! Here we have a remote repository that contains two commits that our local repository does not have."
|
||||
],
|
||||
"afterMarkdowns": [
|
||||
"There we go! Commits `C2` and `C3` were downloaded to our local repository, and our remote branch was updated to reflect the status of the remote repository."
|
||||
],
|
||||
"command": "git fetch",
|
||||
"beforeCommand": "git clone; git fakeTeamwork 2"
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"### What fetch does",
|
||||
"",
|
||||
"`git fetch` performs two main steps, and two main steps only. It:",
|
||||
"",
|
||||
"* downloads the commits that the remote has but are missing from our local repository, and...",
|
||||
"* updates where our remote branches point (for instance, `o/master`)",
|
||||
"",
|
||||
"`git fetch` essentially it brings our _local_ representation of the remote repository into synchronization with what the _actual_ remote repository looks like (right now).",
|
||||
"",
|
||||
"It does this by talking to the remote repository, usually through the internet (via a protocol like `http://` or `git://`).",
|
||||
""
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"### What fetch doesn't do",
|
||||
"",
|
||||
"`git fetch`, however, does not change anything about _your_ local repository. It will not update your `master` branch or change anything about how your filesystem looks right now.",
|
||||
"",
|
||||
"This is important to understand because a lot of developers think that running `git fetch` will make their local repository reflect the state of `origin`. It may download all the necessary data to do that, but it does _not_ actually change any of your local files.",
|
||||
"",
|
||||
"So in this sense, you can think of running `git fetch` as a download step. The steps to reflect the changes of the newly-downloaded commits will explained in following lessons :D"
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"To finish the level, simply `git fetch` and download all the commits!"
|
||||
]
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
"en_US": {
|
||||
"childViews": [
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"## Git Fetch",
|
||||
"",
|
||||
"Working with git remotes really just boils down to transferring data _to_ and _from_ other repositories. As long as we can send commits back and forth, we can share any type of update that is tracked by git (and thus share work, new files, new ideas, love letters, etc etc).",
|
||||
"",
|
||||
"In this lesson we will learn how to fetch data _from_ a remote repository -- the command for this is conveniently named `git fetch`."
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "GitDemonstrationView",
|
||||
"options": {
|
||||
"beforeMarkdowns": [
|
||||
"Before getting into the details of `git fetch`, let's see it in action! Here we have a remote repository that contains two commits that our local repository does not have."
|
||||
],
|
||||
"afterMarkdowns": [
|
||||
"There we go! Commits `C2` and `C3` were downloaded to our local repository, and our remote branch was updated to reflect the status of the remote repository."
|
||||
],
|
||||
"command": "git fetch",
|
||||
"beforeCommand": "git clone; git fakeTeamwork 2"
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"### What fetch does",
|
||||
"",
|
||||
"`git fetch` performs two main steps, and two main steps only. It:",
|
||||
"",
|
||||
"* downloads the commits that the remote has but are missing from our local repository, and...",
|
||||
"* updates where our remote branches point (for instance, `o/master`)",
|
||||
"",
|
||||
"`git fetch` essentially it brings our _local_ representation of the remote repository into synchronization with what the _actual_ remote repository looks like (right now).",
|
||||
"",
|
||||
"It does this by talking to the remote repository, usually through the internet (via a protocol like `http://` or `git://`).",
|
||||
""
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"### What fetch doesn't do",
|
||||
"",
|
||||
"`git fetch`, however, does not change anything about _your_ local repository. It will not update your `master` branch or change anything about how your filesystem looks right now.",
|
||||
"",
|
||||
"This is important to understand because a lot of developers think that running `git fetch` will make their local repository reflect the state of `origin`. It may download all the necessary data to do that, but it does _not_ actually change any of your local files.",
|
||||
"",
|
||||
"So in this sense, you can think of running `git fetch` as a download step. The steps to reflect the changes of the newly-downloaded commits will explained in following lessons :D"
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"To finish the level, simply `git fetch` and download all the commits!"
|
||||
]
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
};
|
||||
|
||||
|
|
@ -25870,6 +25871,7 @@ function getMockVisualization() {
|
|||
var treeString = options.treeString;
|
||||
|
||||
var headless = new HeadlessGit();
|
||||
headless.gitEngine.loadTreeFromString(treeString);
|
||||
return {
|
||||
customEvents: {
|
||||
on: function(key, cb, context) {
|
||||
|
|
@ -41778,7 +41780,7 @@ require.define("/src/levels/remote/clone.js",function(require,module,exports,__d
|
|||
"Up until this point, Learn Git Branching has focused on teaching the basics of _local_ repository work (branching, merging, rebasing, etc). However now that we want to learn about remote repository work, we need a command to set up the environment for those lessons. `git clone` will be that command",
|
||||
"",
|
||||
"Technically, `git clone` in the real world is the command you'll use to create _local_ copies of remote repositories (from github for example). We use this command a bit differently in Learn Git Branching though -- `git clone` actually makes a remote repository out of your local one. Sure it's technically the opposite meaning of the real command, but it helps build the connection between cloning and remote repository work, so let's just run with it for now.",
|
||||
"",
|
||||
""
|
||||
]
|
||||
}
|
||||
},
|
||||
|
|
@ -41824,75 +41826,75 @@ require.define("/src/levels/remote/fetch.js",function(require,module,exports,__d
|
|||
"en_US": "just run git fetch!"
|
||||
},
|
||||
"startDialog": {
|
||||
"en_US": {
|
||||
"childViews": [
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"## Git Fetch",
|
||||
"",
|
||||
"Working with git remotes really just boils down to transferring data _to_ and _from_ other repositories. As long as we can send commits back and forth, we can share any type of update that is tracked by git (and thus share work, new files, new ideas, love letters, etc etc).",
|
||||
"",
|
||||
"In this lesson we will learn how to fetch data _from_ a remote repository -- the command for this is conveniently named `git fetch`."
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "GitDemonstrationView",
|
||||
"options": {
|
||||
"beforeMarkdowns": [
|
||||
"Before getting into the details of `git fetch`, let's see it in action! Here we have a remote repository that contains two commits that our local repository does not have."
|
||||
],
|
||||
"afterMarkdowns": [
|
||||
"There we go! Commits `C2` and `C3` were downloaded to our local repository, and our remote branch was updated to reflect the status of the remote repository."
|
||||
],
|
||||
"command": "git fetch",
|
||||
"beforeCommand": "git clone; git fakeTeamwork 2"
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"### What fetch does",
|
||||
"",
|
||||
"`git fetch` performs two main steps, and two main steps only. It:",
|
||||
"",
|
||||
"* downloads the commits that the remote has but are missing from our local repository, and...",
|
||||
"* updates where our remote branches point (for instance, `o/master`)",
|
||||
"",
|
||||
"`git fetch` essentially it brings our _local_ representation of the remote repository into synchronization with what the _actual_ remote repository looks like (right now).",
|
||||
"",
|
||||
"It does this by talking to the remote repository, usually through the internet (via a protocol like `http://` or `git://`).",
|
||||
""
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"### What fetch doesn't do",
|
||||
"",
|
||||
"`git fetch`, however, does not change anything about _your_ local repository. It will not update your `master` branch or change anything about how your filesystem looks right now.",
|
||||
"",
|
||||
"This is important to understand because a lot of developers think that running `git fetch` will make their local repository reflect the state of `origin`. It may download all the necessary data to do that, but it does _not_ actually change any of your local files.",
|
||||
"",
|
||||
"So in this sense, you can think of running `git fetch` as a download step. The steps to reflect the changes of the newly-downloaded commits will explained in following lessons :D"
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"To finish the level, simply `git fetch` and download all the commits!"
|
||||
]
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
"en_US": {
|
||||
"childViews": [
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"## Git Fetch",
|
||||
"",
|
||||
"Working with git remotes really just boils down to transferring data _to_ and _from_ other repositories. As long as we can send commits back and forth, we can share any type of update that is tracked by git (and thus share work, new files, new ideas, love letters, etc etc).",
|
||||
"",
|
||||
"In this lesson we will learn how to fetch data _from_ a remote repository -- the command for this is conveniently named `git fetch`."
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "GitDemonstrationView",
|
||||
"options": {
|
||||
"beforeMarkdowns": [
|
||||
"Before getting into the details of `git fetch`, let's see it in action! Here we have a remote repository that contains two commits that our local repository does not have."
|
||||
],
|
||||
"afterMarkdowns": [
|
||||
"There we go! Commits `C2` and `C3` were downloaded to our local repository, and our remote branch was updated to reflect the status of the remote repository."
|
||||
],
|
||||
"command": "git fetch",
|
||||
"beforeCommand": "git clone; git fakeTeamwork 2"
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"### What fetch does",
|
||||
"",
|
||||
"`git fetch` performs two main steps, and two main steps only. It:",
|
||||
"",
|
||||
"* downloads the commits that the remote has but are missing from our local repository, and...",
|
||||
"* updates where our remote branches point (for instance, `o/master`)",
|
||||
"",
|
||||
"`git fetch` essentially it brings our _local_ representation of the remote repository into synchronization with what the _actual_ remote repository looks like (right now).",
|
||||
"",
|
||||
"It does this by talking to the remote repository, usually through the internet (via a protocol like `http://` or `git://`).",
|
||||
""
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"### What fetch doesn't do",
|
||||
"",
|
||||
"`git fetch`, however, does not change anything about _your_ local repository. It will not update your `master` branch or change anything about how your filesystem looks right now.",
|
||||
"",
|
||||
"This is important to understand because a lot of developers think that running `git fetch` will make their local repository reflect the state of `origin`. It may download all the necessary data to do that, but it does _not_ actually change any of your local files.",
|
||||
"",
|
||||
"So in this sense, you can think of running `git fetch` as a download step. The steps to reflect the changes of the newly-downloaded commits will explained in following lessons :D"
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"To finish the level, simply `git fetch` and download all the commits!"
|
||||
]
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
};
|
||||
|
||||
|
|
|
|||
1
build/bundle.min.d2ec7de8.js
Normal file
1
build/bundle.min.d2ec7de8.js
Normal file
File diff suppressed because one or more lines are too long
1
build/bundle.min.js
vendored
Normal file
1
build/bundle.min.js
vendored
Normal file
File diff suppressed because one or more lines are too long
|
|
@ -445,7 +445,7 @@
|
|||
For a much easier time perusing the source, see the individual files at:
|
||||
https://github.com/pcottle/learnGitBranching
|
||||
-->
|
||||
<script src="build/bundle.js"></script>
|
||||
<script src="build/bundle.min.d2ec7de8.js"></script>
|
||||
|
||||
<!-- The advantage of github pages: super-easy, simple, slick static hostic.
|
||||
The downside? No raw logs to parse for analytics, so I have to include
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ exports.level = {
|
|||
"Up until this point, Learn Git Branching has focused on teaching the basics of _local_ repository work (branching, merging, rebasing, etc). However now that we want to learn about remote repository work, we need a command to set up the environment for those lessons. `git clone` will be that command",
|
||||
"",
|
||||
"Technically, `git clone` in the real world is the command you'll use to create _local_ copies of remote repositories (from github for example). We use this command a bit differently in Learn Git Branching though -- `git clone` actually makes a remote repository out of your local one. Sure it's technically the opposite meaning of the real command, but it helps build the connection between cloning and remote repository work, so let's just run with it for now.",
|
||||
"",
|
||||
""
|
||||
]
|
||||
}
|
||||
},
|
||||
|
|
|
|||
|
|
@ -9,74 +9,74 @@ exports.level = {
|
|||
"en_US": "just run git fetch!"
|
||||
},
|
||||
"startDialog": {
|
||||
"en_US": {
|
||||
"childViews": [
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"## Git Fetch",
|
||||
"",
|
||||
"Working with git remotes really just boils down to transferring data _to_ and _from_ other repositories. As long as we can send commits back and forth, we can share any type of update that is tracked by git (and thus share work, new files, new ideas, love letters, etc etc).",
|
||||
"",
|
||||
"In this lesson we will learn how to fetch data _from_ a remote repository -- the command for this is conveniently named `git fetch`."
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "GitDemonstrationView",
|
||||
"options": {
|
||||
"beforeMarkdowns": [
|
||||
"Before getting into the details of `git fetch`, let's see it in action! Here we have a remote repository that contains two commits that our local repository does not have."
|
||||
],
|
||||
"afterMarkdowns": [
|
||||
"There we go! Commits `C2` and `C3` were downloaded to our local repository, and our remote branch was updated to reflect the status of the remote repository."
|
||||
],
|
||||
"command": "git fetch",
|
||||
"beforeCommand": "git clone; git fakeTeamwork 2"
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"### What fetch does",
|
||||
"",
|
||||
"`git fetch` performs two main steps, and two main steps only. It:",
|
||||
"",
|
||||
"* downloads the commits that the remote has but are missing from our local repository, and...",
|
||||
"* updates where our remote branches point (for instance, `o/master`)",
|
||||
"",
|
||||
"`git fetch` essentially it brings our _local_ representation of the remote repository into synchronization with what the _actual_ remote repository looks like (right now).",
|
||||
"",
|
||||
"It does this by talking to the remote repository, usually through the internet (via a protocol like `http://` or `git://`).",
|
||||
""
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"### What fetch doesn't do",
|
||||
"",
|
||||
"`git fetch`, however, does not change anything about _your_ local repository. It will not update your `master` branch or change anything about how your filesystem looks right now.",
|
||||
"",
|
||||
"This is important to understand because a lot of developers think that running `git fetch` will make their local repository reflect the state of `origin`. It may download all the necessary data to do that, but it does _not_ actually change any of your local files.",
|
||||
"",
|
||||
"So in this sense, you can think of running `git fetch` as a download step. The steps to reflect the changes of the newly-downloaded commits will explained in following lessons :D"
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"To finish the level, simply `git fetch` and download all the commits!"
|
||||
]
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
"en_US": {
|
||||
"childViews": [
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"## Git Fetch",
|
||||
"",
|
||||
"Working with git remotes really just boils down to transferring data _to_ and _from_ other repositories. As long as we can send commits back and forth, we can share any type of update that is tracked by git (and thus share work, new files, new ideas, love letters, etc etc).",
|
||||
"",
|
||||
"In this lesson we will learn how to fetch data _from_ a remote repository -- the command for this is conveniently named `git fetch`."
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "GitDemonstrationView",
|
||||
"options": {
|
||||
"beforeMarkdowns": [
|
||||
"Before getting into the details of `git fetch`, let's see it in action! Here we have a remote repository that contains two commits that our local repository does not have."
|
||||
],
|
||||
"afterMarkdowns": [
|
||||
"There we go! Commits `C2` and `C3` were downloaded to our local repository, and our remote branch was updated to reflect the status of the remote repository."
|
||||
],
|
||||
"command": "git fetch",
|
||||
"beforeCommand": "git clone; git fakeTeamwork 2"
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"### What fetch does",
|
||||
"",
|
||||
"`git fetch` performs two main steps, and two main steps only. It:",
|
||||
"",
|
||||
"* downloads the commits that the remote has but are missing from our local repository, and...",
|
||||
"* updates where our remote branches point (for instance, `o/master`)",
|
||||
"",
|
||||
"`git fetch` essentially it brings our _local_ representation of the remote repository into synchronization with what the _actual_ remote repository looks like (right now).",
|
||||
"",
|
||||
"It does this by talking to the remote repository, usually through the internet (via a protocol like `http://` or `git://`).",
|
||||
""
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"### What fetch doesn't do",
|
||||
"",
|
||||
"`git fetch`, however, does not change anything about _your_ local repository. It will not update your `master` branch or change anything about how your filesystem looks right now.",
|
||||
"",
|
||||
"This is important to understand because a lot of developers think that running `git fetch` will make their local repository reflect the state of `origin`. It may download all the necessary data to do that, but it does _not_ actually change any of your local files.",
|
||||
"",
|
||||
"So in this sense, you can think of running `git fetch` as a download step. The steps to reflect the changes of the newly-downloaded commits will explained in following lessons :D"
|
||||
]
|
||||
}
|
||||
},
|
||||
{
|
||||
"type": "ModalAlert",
|
||||
"options": {
|
||||
"markdowns": [
|
||||
"To finish the level, simply `git fetch` and download all the commits!"
|
||||
]
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
};
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue