Update all files to use {% data %} (#15253)
* Add back changes from prior to purge * Manually fix some invalid Liquid * Updoot render-content * Improve test messages to show correct output * Run el scripto * Pass the remaining test
This commit is contained in:
@@ -13,7 +13,7 @@ versions:
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** {{ site.data.reusables.organizations.owners-and-admins-can }} manage webhooks for an organization. {{ site.data.reusables.organizations.new-org-permissions-more-info }}
|
||||
**Tip:** {% data reusables.organizations.owners-and-admins-can %} manage webhooks for an organization. {% data reusables.organizations.new-org-permissions-more-info %}
|
||||
|
||||
{% endtip %}
|
||||
|
||||
@@ -21,9 +21,9 @@ Webhooks can be triggered whenever a variety of actions are performed on a repos
|
||||
|
||||
* A repository is pushed to
|
||||
* A pull request is opened
|
||||
* A {{ site.data.variables.product.prodname_pages }} site is built
|
||||
* A {% 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.
|
||||
Using the {% 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)."
|
||||
|
||||
@@ -7,9 +7,9 @@ versions:
|
||||
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.
|
||||
To automate common tasks, back up your data, or create integrations that extend {% data variables.product.product_name %}, you can use the {% 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/).
|
||||
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 [{% data variables.product.prodname_dotcom %} Developer blog](https://developer.github.com/changes/).
|
||||
|
||||
### Further reading
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@ 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.'
|
||||
intro: 'You can use OAuth tokens to interact with {% data variables.product.product_name %} via automated scripts.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -19,18 +19,18 @@ Create a personal access token on your application settings page. For more infor
|
||||
{% 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 }}
|
||||
- {% data reusables.user_settings.review_oauth_tokens_tip %}
|
||||
{% else %}
|
||||
**Tip:** {{ site.data.reusables.user_settings.review_oauth_tokens_tip }}
|
||||
**Tip:** {% 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 %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
|
||||
|
||||
### Step 2: Clone a repository
|
||||
|
||||
{{ site.data.reusables.command_line.providing-token-as-password }}
|
||||
{% 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)."
|
||||
|
||||
|
||||
Reference in New Issue
Block a user