jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-23 11:54:18 -05:00
Code Issues Projects Releases Wiki Activity

remove hardcoded instances

Browse Source
This commit is contained in:
mchammer01
2021-04-08 16:43:24 +01:00
parent bb53099485
commit 634d3d5b3c
3 changed files with 6 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
View File

@@ -21,13 +21,13 @@ If you need to share workflows and other {% data variables.product.prodname_acti
### Creating a workflow template ### Creating a workflow template
Workflow templates can be created by users with write access to the organization's `.github` repository. The templates can then be used by organization members who have permission to create workflows. Workflow templates can be used to create new workflows in an organizations' public repositories; to use templates to create workflows in private repositories, the organization must be part of an enterprise or GitHub One plan. Workflow templates can be created by users with write access to the organization's `.github` repository. The templates can then be used by organization members who have permission to create workflows. Workflow templates can be used to create new workflows in an organizations' public repositories; to use templates to create workflows in private repositories, the organization must be part of an enterprise plan.
This procedure demonstrates how to create a workflow template and metadata file. The metadata file describes how the template is presented to users when they are creating a new workflow. This procedure demonstrates how to create a workflow template and metadata file. The metadata file describes how the template is presented to users when they are creating a new workflow.
1. If it doesn't already exist, create a new public repository named `.github` in your organization. 1. If it doesn't already exist, create a new public repository named `.github` in your organization.
1. Create a directory named `workflow-templates`. 2. Create a directory named `workflow-templates`.
1. Create your new workflow file inside the `workflow-templates` directory. 3. Create your new workflow file inside the `workflow-templates` directory.
If you need to refer to a repository's default branch, you can use the `$default-branch` placeholder. When a workflow is created using your template, the placeholder will be automatically replaced with the name of the repository's default branch. If you need to refer to a repository's default branch, you can use the `$default-branch` placeholder. When a workflow is created using your template, the placeholder will be automatically replaced with the name of the repository's default branch.
@@ -52,7 +52,7 @@ This procedure demonstrates how to create a workflow template and metadata file.
- name: Run a one-line script - name: Run a one-line script
run: echo Hello from Octo Organization run: echo Hello from Octo Organization
``` ```
1. Create a metadata file inside the `workflow-templates` directory. The metadata file must have the same name as the workflow file, but instead of the `.yml` extension, it must be appended with `.properties.json`. For example, this file named `octo-organization-ci.properties.json` contains the metadata for a workflow file named `octo-organization-ci.yml`: 4. Create a metadata file inside the `workflow-templates` directory. The metadata file must have the same name as the workflow file, but instead of the `.yml` extension, it must be appended with `.properties.json`. For example, this file named `octo-organization-ci.properties.json` contains the metadata for a workflow file named `octo-organization-ci.yml`:
```yaml ```yaml
{ {
"name": "Octo Organization Workflow", "name": "Octo Organization Workflow",

4
content/github/site-policy-deprecated/github-enterprise-subscription-agreement.md
View File

@@ -15,7 +15,7 @@ BY CLICKING THE "I AGREE" OR SIMILAR BUTTON OR BY USING ANY OF THE PRODUCTS (DEF
This Agreement applies to the following GitHub offerings, as further defined below (collectively, the **"Products"**): This Agreement applies to the following GitHub offerings, as further defined below (collectively, the **"Products"**):
- GitHub Enterprise (comprised of GitHub Enterprise Server, which may include Add-On Software, and GitHub Enterprise Cloud) and GitHub One; - GitHub Enterprise (comprised of GitHub Enterprise Server, which may include Add-On Software, and GitHub Enterprise Cloud);
- Any Beta Previews; - Any Beta Previews;
@@ -406,8 +406,6 @@ Some Service features may be subject to additional terms as set forth in the [Gi
**"GitHub Insights"** or **“Insights”** means the Software feature which provides Customer with metrics, analytics, and recommendations relating to their use of the Software. GitHub Insights does not include legacy features of GitHub including Organization insights and repository insights. **"GitHub Insights"** or **“Insights”** means the Software feature which provides Customer with metrics, analytics, and recommendations relating to their use of the Software. GitHub Insights does not include legacy features of GitHub including Organization insights and repository insights.
**“GitHub One”** means the Product bundle which includes GitHub Enterprise, Advanced Security, Insights, Learning Lab for Enterprise Server, and Premium Plus or Engineering Direct Support.
**"Learning Lab for Enterprise Server"** means the Software feature that enables Users to learn about GitHub functionality, including associated Documentation. **"Learning Lab for Enterprise Server"** means the Software feature that enables Users to learn about GitHub functionality, including associated Documentation.
**"License Key"** means the data file used by the Software's access control mechanism that allows Customer to install, operate, and use the Software. **"License Key"** means the data file used by the Software's access control mechanism that allows Customer to install, operate, and use the Software.

4
content/github/site-policy-deprecated/github-supplemental-terms-for-microsoft-volume-licensing.md
View File

@@ -15,7 +15,7 @@ The following GitHub Supplemental Terms (including any applicable Order Forms) s
These Supplemental Terms apply to the following GitHub Offerings, as further defined below (collectively, the "**Products**"): These Supplemental Terms apply to the following GitHub Offerings, as further defined below (collectively, the "**Products**"):
- GitHub Enterprise (comprised of GitHub Enterprise Server, which may include Add-on Software, and GitHub Enterprise Cloud) and GitHub One; - GitHub Enterprise (comprised of GitHub Enterprise Server, which may include Add-on Software, and GitHub Enterprise Cloud);
- Any related Support; and - Any related Support; and
@@ -274,8 +274,6 @@ In the event of a conflict between the Supplemental Terms, on one hand, and an O
**"GitHub Insights"** or **“Insights”** means the Software feature which provides Customer with metrics, analytics, and recommendations relating to their use of the Software. GitHub Insights does not include legacy features of GitHub including organization insights and repository insights. **"GitHub Insights"** or **“Insights”** means the Software feature which provides Customer with metrics, analytics, and recommendations relating to their use of the Software. GitHub Insights does not include legacy features of GitHub including organization insights and repository insights.
**“GitHub One”** means the Product bundle which includes GitHub Enterprise, Advanced Security, Insights, Learning Lab for Enterprise Server, and Premium Plus or Engineering Direct Support.
**"Learning Lab for Enterprise Server"** means the Software feature that enables Users to learn about GitHub functionality, including associated Documentation. **"Learning Lab for Enterprise Server"** means the Software feature that enables Users to learn about GitHub functionality, including associated Documentation.
**"License Key"** means the data file used by the Software's access control mechanism that allows Customer to install, operate, and use the Software. **"License Key"** means the data file used by the Software's access control mechanism that allows Customer to install, operate, and use the Software.