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)."
|
||||
|
||||
Reference in New Issue
Block a user