Skip to content

Commit 3049ec8

Browse files
authored
Merge branch 'main' into patch-1
2 parents 93acf31 + 5a0b54b commit 3049ec8

29 files changed

Lines changed: 21972 additions & 2290 deletions

content/actions/managing-workflow-runs/reviewing-deployments.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ versions:
1313

1414
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.
1515

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)."
1717

1818
### Approving or rejecting a job
1919

content/actions/reference/environments.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,8 @@ Secrets stored in an environment are only available to workflow jobs that refere
5656
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.
5757
1. Configure any environment protection rules or environment secrets.
5858

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+
5961
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.
6062

6163
### Referencing an environment
@@ -77,3 +79,5 @@ Deleting an environment will delete all secrets and protection rules associated
7779
{% data reusables.github-actions.sidebar-environment %}
7880
1. Next the the environment that you want to delete, click {% octicon "trashcan" aria-label="The trashcan icon" %}.
7981
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)."

content/admin/configuration/configuring-code-scanning-for-your-appliance.md

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,6 @@ For the users of {% data variables.product.product_location %} to be able to ena
4242
![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png)
4343
{% data reusables.enterprise_management_console.save-settings %}
4444

45-
4645
### Running {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_actions %}
4746

4847
#### Setting up a self-hosted runner
@@ -89,3 +88,25 @@ The {% data variables.product.prodname_codeql_runner %} is a command-line tool t
8988
1. Under "{% data variables.product.prodname_advanced_security %}", unselect **{% data variables.product.prodname_code_scanning_capc %}**.
9089
![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/code-scanning-disable.png)
9190
{% 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 %}.
105+
```shell
106+
ghe-config app.minio.enabled false
107+
ghe-config app.code-scanning.enabled false
108+
```
109+
3. Apply the configuration.
110+
```shell
111+
ghe-config-apply
112+
```

content/graphql/guides/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,3 +20,5 @@ versions:
2020
{% link_in_list /using-the-explorer %}
2121

2222
{% link_in_list /managing-enterprise-accounts %}
23+
24+
{% link_in_list /using-the-graphql-api-for-discussions %}

0 commit comments

Comments
 (0)