You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/actions/managing-workflow-runs/reviewing-deployments.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ versions:
13
13
14
14
Jobs that reference an environment configured with required reviewers will wait for an approval before starting. While a job is awaiting approval, it has a status of "Waiting". If a job is not approved within 30 days, the workflow run will be automatically canceled.
15
15
16
-
For more information about environments and required approvals, see "[Environments](/actions/reference/environments)."
16
+
For more information about environments and required approvals, see "[Environments](/actions/reference/environments)." For information about how to review deployments with the REST API, see "[Workflow Runs](/rest/reference/actions#workflow-runs)."
Copy file name to clipboardExpand all lines: content/actions/reference/environments.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,6 +56,8 @@ Secrets stored in an environment are only available to workflow jobs that refere
56
56
1. Enter a name for the environment, then click **Configure environment**. Environment names are not case sensitive. An environment name may not exceed 255 characters and must be unique within the repository.
57
57
1. Configure any environment protection rules or environment secrets.
58
58
59
+
You can also create and configure environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)" and "[Secrets](/rest/reference/actions#secrets)."
60
+
59
61
Running a workflow that references an environment that does not exist will create an environment with the referenced name. The newly created environment will not have any protection rules or secrets configured. Anyone that can edit workflows in the repository can create environments via a workflow file, but only repository admins can configure the environment.
60
62
61
63
### Referencing an environment
@@ -77,3 +79,5 @@ Deleting an environment will delete all secrets and protection rules associated
77
79
{% data reusables.github-actions.sidebar-environment %}
78
80
1. Next the the environment that you want to delete, click {% octicon "trashcan" aria-label="The trashcan icon" %}.
79
81
2. Click **I understand, delete this environment**.
82
+
83
+
You can also delete environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)."
Copy file name to clipboardExpand all lines: content/admin/configuration/configuring-code-scanning-for-your-appliance.md
+22-1Lines changed: 22 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,6 @@ For the users of {% data variables.product.product_location %} to be able to ena
42
42

43
43
{% data reusables.enterprise_management_console.save-settings %}
44
44
45
-
46
45
### Running {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_actions %}
47
46
48
47
#### Setting up a self-hosted runner
@@ -89,3 +88,25 @@ The {% data variables.product.prodname_codeql_runner %} is a command-line tool t
89
88
1. Under "{% data variables.product.prodname_advanced_security %}", unselect **{% data variables.product.prodname_code_scanning_capc %}**.
90
89

91
90
{% data reusables.enterprise_management_console.save-settings %}
91
+
92
+
### Enabling or disabling {% data variables.product.prodname_code_scanning %} via the administrative shell (SSH)
93
+
94
+
You can enable or disable {% data variables.product.prodname_code_scanning %} programmatically on {% data variables.product.product_location %}. For example, you can enable {% data variables.product.prodname_code_scanning %} with your infrastructure-as-code tooling when you deploy an instance for staging or disaster recovery.
95
+
96
+
For more information about the administrative shell and command-line utilities for {% data variables.product.prodname_ghe_server %}, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[Command-line utilities](/admin/configuration/command-line-utilities#ghe-config)."
97
+
98
+
1. SSH into {% data variables.product.product_location %}.
99
+
1. Enable {% data variables.product.prodname_code_scanning %}.
100
+
```shell
101
+
ghe-config app.minio.enabled true
102
+
ghe-config app.code-scanning.enabled true
103
+
```
104
+
2. Optionally, disable {% data variables.product.prodname_code_scanning %}.
0 commit comments