Hello git history spelunker!

Are you looking for something? Here is all of the GitHub Docs history in one single commit. Enjoy! 🎉

content/github/extending-github/about-webhooks.md

@@ -0,0 +1,29 @@
+---
+title: About webhooks
+redirect_from:
+  - /post-receive-hooks/
+  - /articles/post-receive-hooks/
+  - /articles/creating-webhooks/
+  - /articles/about-webhooks
+intro: Webhooks provide a way for notifications to be delivered to an external web server whenever certain actions occur on a repository or organization.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+
+{% tip %}
+
+**Tip:** {{ site.data.reusables.organizations.owners-and-admins-can }} manage webhooks for an organization. {{ site.data.reusables.organizations.new-org-permissions-more-info }}
+
+{% endtip %}
+
+Webhooks can be triggered whenever a variety of actions are performed on a repository or an organization. For example, you can configure a webhook to execute whenever:
+
+* A repository is pushed to
+* A pull request is opened
+* A {{ site.data.variables.product.prodname_pages }} site is built
+* A new member is added to a team
+
+Using the {{ site.data.variables.product.product_name }} API, you can make these webhooks update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server.
+
+To set up a new webhook, you'll need access to an external server and familiarity with the technical procedures involved. For help on building a webhook, including a full list of actions you can associate with, see "[Webhooks](/webhooks)."

content/github/extending-github/getting-started-with-the-api.md

@@ -0,0 +1,17 @@
+---
+title: Getting started with the API
+redirect_from:
+  - /articles/getting-started-with-the-api
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+
+To automate common tasks, back up your data, or create integrations that extend {{ site.data.variables.product.product_name }}, you can use the {{ site.data.variables.product.product_name }} API.
+
+For more information about the API, see the [GitHub REST API](/rest) and [GitHub GraphQL API](/graphql). You can also stay current with API-related news by following the [{{ site.data.variables.product.prodname_dotcom }} Developer blog](https://developer.github.com/changes/).
+
+### Further reading
+
+- "[Backing up a repository](/articles/backing-up-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
+- "[About integrations](/articles/about-integrations)"{% endif %}

content/github/extending-github/git-automation-with-oauth-tokens.md

@@ -0,0 +1,45 @@
+---
+title: Git automation with OAuth tokens
+redirect_from:
+  - /articles/git-over-https-using-oauth-token/
+  - /articles/git-over-http-using-oauth-token/
+  - /articles/git-automation-with-oauth-tokens
+intro: 'You can use OAuth tokens to interact with {{ site.data.variables.product.product_name }} via automated scripts.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+
+### Step 1: Get an OAuth token
+
+Create a personal access token on your application settings page. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+{% tip %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+**Tips:**
+- You must verify your email address before you can create a personal access token. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
+- {{ site.data.reusables.user_settings.review_oauth_tokens_tip }}
+{% else %}
+**Tip:** {{ site.data.reusables.user_settings.review_oauth_tokens_tip }}
+{% endif %}
+
+{% endtip %}
+
+{% if currentVersion == "free-pro-team@latest" %}{{ site.data.reusables.user_settings.removes-personal-access-tokens }}{% endif %}
+
+### Step 2: Clone a repository
+
+{{ site.data.reusables.command_line.providing-token-as-password }}
+
+To avoid these prompts, you can use Git password caching. For information, see "[Caching your GitHub credentials in Git](/github/using-git/caching-your-github-credentials-in-git)."
+
+{% warning %}
+
+**Warning**: Tokens have read/write access and should be treated like passwords. If you enter your token into the clone URL when cloning or adding a remote, Git writes it to your _.git/config_ file in plain text, which is a security risk.
+
+{% endwarning %}
+
+### Further reading
+
+- "[Authorizing OAuth Apps](/v3/oauth/)"

content/github/extending-github/index.md

@@ -0,0 +1,17 @@
+---
+title: Extending GitHub
+redirect_from:
+  - /categories/86/articles/
+  - /categories/automation/
+  - /categories/extending-github
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+
+
+### Table of Contents
+
+{% link_in_list /getting-started-with-the-api %}
+{% link_in_list /git-automation-with-oauth-tokens %}
+{% link_in_list /about-webhooks %}