Merge branch 'script-to-use-short-versions' of github.com:github/docs-internal into script-to-use-short-versions
This commit is contained in:
@@ -66,4 +66,4 @@ By default, we notify people with admin permissions in the affected repositories
|
||||
We send security alerts to people with admin permissions in the affected repositories by default. {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository.
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
|
||||
|
||||
@@ -78,7 +78,7 @@ Do **not** use the operators `&&` or `||`. Liquid does not recognize them, and t
|
||||
|
||||
If your content describes a feature that will be included in the next release of GitHub AE, you can use a placeholder version string, `ghae-next`. Before the next GitHub AE release, we will run a script to replace the placeholder with `ghae`.
|
||||
|
||||
For example, you can use this logic before the feature is available in GitHub AE:
|
||||
For example, you can use this logic for a feature that's shipping on GitHub.com and will also be available in a future update to GitHub AE:
|
||||
```
|
||||
{% ifversion fpt or ghae-next %}This is a brand new feature, the likes of which have never been seen at this company before!{% endif %}
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user