Skip to content

Commit 1d959ed

Browse files
Martin Lopesjmarlena
andauthored
Updates for GHAE Actions beta (#18048)
* Added AE version * Renamed draft article * Fixed typo * Added new section for AE * Fixed versioning * Update finding-and-customizing-actions.md * Update using-actions-in-github-ae.md * Apply suggestions from code review Co-authored-by: jmarlena <6732600+jmarlena@users.noreply.github.com> * Update using-actions-in-github-ae.md Co-authored-by: jmarlena <6732600+jmarlena@users.noreply.github.com>
1 parent c3bd124 commit 1d959ed

3 files changed

Lines changed: 27 additions & 0 deletions

File tree

content/actions/learn-github-actions/finding-and-customizing-actions.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,12 @@ outputs:
114114
description: "Path to results file"
115115
```
116116

117+
{% if currentVersion == "github-ae@latest" %}
118+
### Using the actions included with {% data variables.product.prodname_ghe_managed %}
119+
120+
By default, you can use most of the official {% data variables.product.prodname_dotcom %}-authored actions in {% data variables.product.prodname_ghe_managed %}. For more information, see "[Using actions in {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-actions-in-github-ae)."
121+
{% endif %}
122+
117123
### Referencing an action in the same repository where a workflow file uses the action
118124

119125
If an action is defined in the same repository where your workflow file uses the action, you can reference the action with either the ‌`{owner}/{repo}@{ref}` or `./path/to/dir` syntax in your workflow file.

content/admin/github-actions/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ versions:
1616

1717
{% topic_link_in_list /using-github-actions-in-github-ae %}
1818
{% link_in_list /getting-started-with-github-actions-for-github-ae %}
19+
{% link_in_list /using-actions-in-github-ae %}
1920

2021
{% topic_link_in_list /enabling-github-actions-for-github-enterprise-server %}
2122
{% link_in_list /getting-started-with-github-actions-for-github-enterprise-server %}
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
title: Using actions in GitHub AE
3+
intro: '{% data variables.product.prodname_ghe_managed %} includes most of the {% data variables.product.prodname_dotcom %}-authored actions.'
4+
versions:
5+
github-ae: '*'
6+
---
7+
8+
{% data reusables.actions.ae-beta %}
9+
10+
{% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community.
11+
12+
### Official actions bundled with {% data variables.product.prodname_ghe_managed %}
13+
14+
Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.prodname_ghe_managed %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}. When your {% data variables.product.prodname_ghe_managed %} instance is updated, the bundled official actions are also updated.
15+
16+
The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. To see which of the official actions are included, browse to the following organizations on your instance:
17+
- <code>https://<em>HOSTNAME</em>/actions</code>
18+
- <code>https://<em>HOSTNAME</em>/github</code>
19+
20+
Each action's files are kept in a repository in the `actions` and `github` organizations. Each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action.

0 commit comments

Comments
 (0)