Skip to content

Commit 28b9d63

Browse files
committed
added gitcasts everywhere I could
1 parent 7d439bc commit 28b9d63

File tree

9 files changed

+24
-4
lines changed

9 files changed

+24
-4
lines changed

text/07_Normal_Workflow/0_ Normal_Workflow.markdown

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,4 +53,6 @@ system to start tracking changes to a new file. Git's "add" command
5353
does something simpler and more powerful: `git add` is used both for new
5454
and newly modified files, and in both cases it takes a snapshot of the
5555
given files and stages that content in the index, ready for inclusion in
56-
the next commit.
56+
the next commit.
57+
58+
[gitcast:c2_normal_workflow]("GitCast #2: Normal Workflow")

text/08_Basic_Branching_and_Merging/0_ Basic_Branching_and_Merging.markdown

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -162,3 +162,5 @@ commit present in the one is already contained in the other--then git
162162
just performs a "fast forward"; the head of the current branch is moved
163163
forward to point at the head of the merged-in branch, without any new
164164
commits being created.
165+
166+
[gitcast:c6-branch-merge]("GitCast #6: Branching and Merging")

text/09_Reviewing_History_Git_Log/0_ Reviewing_History_Git_Log.markdown

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,3 +31,5 @@ Note that git log starts with the most recent commit and works
3131
backwards through the parents; however, since git history can contain
3232
multiple independent lines of development, the particular order that
3333
commits are listed in may be somewhat arbitrary.
34+
35+
[gitcast:c4-git-log]("GitCast #4: Git Log")

text/11_Distributed_Workflows_Clone_Fetch_Push/0_ Distributed_Workflows_Clone_Fetch_Push.markdown

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -235,4 +235,6 @@ the right to push to the same repository. In that case, the correct
235235
solution is to retry the push after first updating your work: either by a
236236
pull, or by a fetch followed by a rebase; see the
237237
<<setting-up-a-shared-repository,next section>> and
238-
linkgit:gitcvs-migration[7] for more.
238+
linkgit:gitcvs-migration[7] for more.
239+
240+
[gitcast:c8-dist-workflow]("GitCast #8: Distributed Workflow")

text/13_Rebasing/0_ Rebasing.markdown

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,3 +68,6 @@ At any point you may use the `--abort` option to abort this process and
6868
return mywork to the state it had before you started the rebase:
6969

7070
$ git rebase --abort
71+
72+
73+
[gitcast:c7-rebase]("GitCast #7: Rebasing")
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,3 @@
11
## Interactive Adding ##
22

3+
[gitcast:c3_add_interactive]("GitCast #3: Interactive Adding")

text/25_Creating_New_Empty_Branches/0_ Creating_New_Empty_Branches.markdown

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,4 +6,6 @@
66
git clean -fdx
77
<do work>
88
git add your files
9-
git commit -m 'Initial commit'
9+
git commit -m 'Initial commit'
10+
11+
[gitcast:c9-empty-branch]("GitCast #7: Creating Empty Branches")

text/34_Git_Submodules/1_Submodules.markdown

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -202,3 +202,5 @@ silently overwritten:
202202
NOTE: The changes are still visible in the submodule's reflog.
203203

204204
This is not the case if you did not commit your changes.
205+
206+
[gitcast:c11-git-submodules]("GitCast #11: Git Submodules")
Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,5 @@
1-
##Git on Windows
1+
## Git on Windows ##
2+
3+
(mSysGit)
4+
5+
[gitcast:c10-windows-git]("GitCast #10: Git on Windows")

0 commit comments

Comments
 (0)