diff options
Diffstat (limited to '_posts')
| -rw-r--r-- | _posts/2009-06-23-security.markdown | 2 | ||||
| -rw-r--r-- | _posts/2009-09-09-removing-sensitive-data.textile | 2 | ||||
| -rw-r--r-- | _posts/2009-09-27-splitting-a-subpath-to-a-new-repo.textile | 2 | ||||
| -rw-r--r-- | _posts/2009-10-10-subtree-merge.textile | 2 | ||||
| -rw-r--r-- | _posts/2010-01-12-privacy.markdown | 2 | ||||
| -rw-r--r-- | _posts/2010-01-12-terms.markdown | 2 | ||||
| -rw-r--r-- | _posts/2010-01-15-dmca.markdown | 2 | ||||
| -rwxr-xr-x | _posts/2010-01-27-remotes.markdown | 2 | ||||
| -rwxr-xr-x | _posts/2010-01-28-git-ignore.markdown | 2 | ||||
| -rwxr-xr-x | _posts/2010-01-29-rebase.markdown | 2 | ||||
| -rw-r--r-- | _posts/2010-03-02-changing-author-info.markdown | 2 |
11 files changed, 11 insertions, 11 deletions
diff --git a/_posts/2009-06-23-security.markdown b/_posts/2009-06-23-security.markdown index 9c58758..b0be78a 100644 --- a/_posts/2009-06-23-security.markdown +++ b/_posts/2009-06-23-security.markdown @@ -1,7 +1,7 @@ --- layout: default title: GitHub Security -categories: "Site Policy" +categories: site_policy --- We know your code is extremely important to you and your business and we're very protective of it. After all, GitHub's code is hosted on GitHub, too! diff --git a/_posts/2009-09-09-removing-sensitive-data.textile b/_posts/2009-09-09-removing-sensitive-data.textile index bd8285a..f16b50c 100644 --- a/_posts/2009-09-09-removing-sensitive-data.textile +++ b/_posts/2009-09-09-removing-sensitive-data.textile @@ -2,7 +2,7 @@ layout: default title: Removing sensitive data description: Dealing with accidentally committed passwords or other sensitive information -categories: popular, "Git ninjutsu" +categories: popular, git_ninjutsu --- From time to time users accidentally commit data like passwords or keys into a git repo. While you can use @git rm@ to remove the file, it will still be in the repo's history. Fortunately, git makes it fairly simple to remove the file from the entire repo history. diff --git a/_posts/2009-09-27-splitting-a-subpath-to-a-new-repo.textile b/_posts/2009-09-27-splitting-a-subpath-to-a-new-repo.textile index 0013d16..b54836c 100644 --- a/_posts/2009-09-27-splitting-a-subpath-to-a-new-repo.textile +++ b/_posts/2009-09-27-splitting-a-subpath-to-a-new-repo.textile @@ -2,7 +2,7 @@ layout: default title: Splitting a subpath out into a new repo description: How to generate a new repo from a subpath, retaining history. -categories: "Git ninjutsu" +categories: git_ninjutsu --- From time to time you may find that you want to make a new repo from a subpath of an existing repo. Perhaps you're moving some code out into a library or just want to have a common submodule across projects. Thanks to git, it's easy to do this without losing the history of that subpath in the process. diff --git a/_posts/2009-10-10-subtree-merge.textile b/_posts/2009-10-10-subtree-merge.textile index b9d7474..c2b3fd3 100644 --- a/_posts/2009-10-10-subtree-merge.textile +++ b/_posts/2009-10-10-subtree-merge.textile @@ -2,7 +2,7 @@ layout: default title: Working with subtree merge description: How to use subtree merge to merge one repo into another as a subpath. -categories: "Git ninjutsu" +categories: git_ninjutsu --- There are times when submodules are not adequate for the task at hand. For example, blending multiple repos together into one single repo while still maintaining the histor of each repo. To do this, the subtree merge strategy is a better solution. diff --git a/_posts/2010-01-12-privacy.markdown b/_posts/2010-01-12-privacy.markdown index f2afc90..d83ac0c 100644 --- a/_posts/2010-01-12-privacy.markdown +++ b/_posts/2010-01-12-privacy.markdown @@ -1,7 +1,7 @@ --- layout: default title: GitHub Privacy Policy -categories: "Site Policy" +categories: site_policy --- General Information diff --git a/_posts/2010-01-12-terms.markdown b/_posts/2010-01-12-terms.markdown index 11d4224..5675663 100644 --- a/_posts/2010-01-12-terms.markdown +++ b/_posts/2010-01-12-terms.markdown @@ -1,7 +1,7 @@ --- layout: default title: GitHub Terms of Service -categories: "Site Policy" +categories: site_policy --- By using the GitHub.com web site ("Service"), or any services of GitHub Inc ("GitHub"), you are agreeing to be bound by the following terms and conditions ("Terms of Service"). IF YOU ARE ENTERING INTO THIS AGREEMENT ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY, ITS AFFILIATES AND ALL USERS WHO ACCESS OUR SERVICES THROUGH YOUR ACCOUNT TO THESE TERMS AND CONDITIONS, IN WHICH CASE THE TERMS "YOU" OR "YOUR" SHALL REFER TO SUCH ENTITY, ITS AFFILIATES AND USERS ASSOCIATED WITH IT. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT AGREE WITH THESE TERMS AND CONDITIONS, YOU MUST NOT ACCEPT THIS AGREEMENT AND MAY NOT USE THE SERVICES. diff --git a/_posts/2010-01-15-dmca.markdown b/_posts/2010-01-15-dmca.markdown index 03b7619..4577c3d 100644 --- a/_posts/2010-01-15-dmca.markdown +++ b/_posts/2010-01-15-dmca.markdown @@ -1,7 +1,7 @@ --- layout: default title: DMCA Takedown -categories: "Site Policy" +categories: site_policy --- GitHub, Inc. ("GitHub") supports the protection of intellectual property and asks the users of the website GitHub.com to do the same. It is the policy of GitHub to respond to all notices of alleged copyright infringement. diff --git a/_posts/2010-01-27-remotes.markdown b/_posts/2010-01-27-remotes.markdown index 76b5051..7dafa2c 100755 --- a/_posts/2010-01-27-remotes.markdown +++ b/_posts/2010-01-27-remotes.markdown @@ -2,7 +2,7 @@ layout: default title: Working with remotes description: Pushing, fetching, merging and deleting remote branches -categories: "Everyday git" +categories: everyday_git --- This guide will cover all the basic day-to-day commends you will use with git to interact with remote repos. For push operations you can only interact with repos you own or are a collaborator on. To gain access to a public repo, check out the [forking guide](/forking). diff --git a/_posts/2010-01-28-git-ignore.markdown b/_posts/2010-01-28-git-ignore.markdown index d706c6c..1f1d6a1 100755 --- a/_posts/2010-01-28-git-ignore.markdown +++ b/_posts/2010-01-28-git-ignore.markdown @@ -2,7 +2,7 @@ layout: default title: Ignoring files description: How to tell git to ignore files -categories: "Everyday git" +categories: everyday_git --- From time to time there are files you don't want git to track. There are a few methods of telling git what files to ignore. diff --git a/_posts/2010-01-29-rebase.markdown b/_posts/2010-01-29-rebase.markdown index 11e900a..fd7b9c7 100755 --- a/_posts/2010-01-29-rebase.markdown +++ b/_posts/2010-01-29-rebase.markdown @@ -2,7 +2,7 @@ layout: default title: All your rebase description: Using git rebase to restructure a branch -categories: "Everyday git" +categories: everyday_git --- One often overlooked feature of git is the `git rebase` command. Rebase allows you to easily change a series of commits, reordering, editing, or squashing commits together into a single commit. diff --git a/_posts/2010-03-02-changing-author-info.markdown b/_posts/2010-03-02-changing-author-info.markdown index 47c19ba..0dbab43 100644 --- a/_posts/2010-03-02-changing-author-info.markdown +++ b/_posts/2010-03-02-changing-author-info.markdown @@ -2,7 +2,7 @@ layout: default title: Changing author info description: How to modify author info in your repo's history -categories: "Git ninjutsu" +categories: git_ninjutsu --- If you need to modify the author info in your repo's history, you can do so with this script. |