Merge branch 'main' into hectorsector/fix-contrast-dark
This commit is contained in:
Hector Alfaro
21
.devcontainer/test-custom-devcontainer/Dockerfile
Normal file
21
.devcontainer/test-custom-devcontainer/Dockerfile
Normal file
@@ -0,0 +1,21 @@
|
||||
# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.177.0/containers/javascript-node/.devcontainer/base.Dockerfile
|
||||
|
||||
# [Choice] Node.js version: 16, 14, 12
|
||||
ARG VARIANT="16-buster"
|
||||
FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
|
||||
|
||||
# [Optional] Uncomment this section to install additional OS packages.
|
||||
# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
|
||||
# && apt-get -y install --no-install-recommends <your-package-list-here>
|
||||
|
||||
# [Optional] Uncomment if you want to install an additional version of node using nvm
|
||||
# ARG EXTRA_NODE_VERSION=10
|
||||
# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}"
|
||||
|
||||
# [Optional] Uncomment if you want to install more global node modules
|
||||
# RUN su node -c "npm install -g <your-package-list-here>"
|
||||
|
||||
# Install the GitHub CLI see:
|
||||
# https://github.com/microsoft/vscode-dev-containers/blob/3d59f9fe37edb68f78874620f33dac5a62ef2b93/script-library/docs/github.md
|
||||
COPY library-scripts/github-debian.sh /tmp/library-scripts/
|
||||
RUN apt-get update && bash /tmp/library-scripts/github-debian.sh
|
||||
34
.devcontainer/test-custom-devcontainer/devcontainer.json
Normal file
34
.devcontainer/test-custom-devcontainer/devcontainer.json
Normal file
@@ -0,0 +1,34 @@
|
||||
{
|
||||
"name": "docs.github.com",
|
||||
|
||||
// Set *default* container specific settings.json values on container create.
|
||||
"settings": {
|
||||
"terminal.integrated.shell.linux": "/bin/bash",
|
||||
"cSpell.language": ",en"
|
||||
},
|
||||
|
||||
// Install features. Type 'feature' in the VS Code command palette for a full list.
|
||||
"features": {
|
||||
"git-lfs": "latest"
|
||||
},
|
||||
|
||||
// Visual Studio Code extensions which help authoring for docs.github.com.
|
||||
"extensions": [
|
||||
"dbaeumer.vscode-eslint",
|
||||
"sissel.shopify-liquid",
|
||||
"davidanson.vscode-markdownlint",
|
||||
"bierner.markdown-preview-github-styles",
|
||||
"streetsidesoftware.code-spell-checker"
|
||||
],
|
||||
|
||||
// Use 'forwardPorts' to make a list of ports inside the container available locally.
|
||||
"forwardPorts": [4000],
|
||||
|
||||
// Use 'postCreateCommand' to run commands after the container is created.
|
||||
//"postCreateCommand": "git lfs pull && npm ci",
|
||||
"postCreateCommand": "echo This file was created by the postCreateCommand in the custom devcontainer.json > aaa-TEST.txt",
|
||||
|
||||
// Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
|
||||
"remoteUser": "node"
|
||||
|
||||
}
|
||||
3
.github/workflows/optimize-images.yml
vendored
3
.github/workflows/optimize-images.yml
vendored
@@ -16,7 +16,8 @@ permissions:
|
||||
|
||||
jobs:
|
||||
optimize-images-on-pr:
|
||||
if: github.repository == 'github/docs-internal' || github.repository == 'github/docs'
|
||||
# We can't make commits on forks
|
||||
if: github.repository == 'github/docs-internal'
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Check out repo on head ref
|
||||
|
||||
2
.github/workflows/triage-stale-check.yml
vendored
2
.github/workflows/triage-stale-check.yml
vendored
@@ -24,7 +24,7 @@ jobs:
|
||||
stale-issue-message: 'A stale label has been added to this issue becuase it has been open for 60 days with no activity. To keep this issue open, add a comment within 3 days.'
|
||||
days-before-issue-stale: 60
|
||||
days-before-issue-close: 3
|
||||
exempt-issue-labels: 'help wanted,waiting for review'
|
||||
exempt-issue-labels: 'help wanted,never-stale,waiting for review'
|
||||
stale-pr-message: 'A stale label has been added to this pull request because it has been open 7 days with no activity. To keep this PR open, add a comment or push a commit within 3 days.'
|
||||
days-before-pr-stale: 7
|
||||
days-before-pr-close: 3
|
||||
|
||||
BIN
assets/images/help/codespaces/add-constraint-dropdown-ports.png
Normal file
BIN
assets/images/help/codespaces/add-constraint-dropdown-ports.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 67 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 47 KiB After Width: | Height: | Size: 63 KiB |
BIN
assets/images/help/codespaces/choose-port-visibility-options.png
Normal file
BIN
assets/images/help/codespaces/choose-port-visibility-options.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 35 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 21 KiB After Width: | Height: | Size: 28 KiB |
BIN
assets/images/help/organizations/add-moderators.png
Normal file
BIN
assets/images/help/organizations/add-moderators.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 56 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 15 KiB After Width: | Height: | Size: 25 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 15 KiB After Width: | Height: | Size: 26 KiB |
BIN
assets/images/help/repository/social-preview-transparency.png
Normal file
BIN
assets/images/help/repository/social-preview-transparency.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 168 KiB |
@@ -34,7 +34,7 @@ We recommend that you schedule a maintenance window for at least 30 minutes in t
|
||||
|
||||
|
||||
|
||||
When the instance is in maintenance mode, all normal HTTP and Git access is refused. Git fetch, clone, and push operations are also rejected with an error message indicating that the site is temporarily unavailable. GitHub Actions jobs will not be executed. Visiting the site in a browser results in a maintenance page.
|
||||
When the instance is in maintenance mode, all normal HTTP and Git access is refused. Git fetch, clone, and push operations are also rejected with an error message indicating that the site is temporarily unavailable. In high availability configurations, Git replication will be paused. GitHub Actions jobs will not be executed. Visiting the site in a browser results in a maintenance page.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -54,10 +54,9 @@ AMIs for {% data variables.product.prodname_ghe_server %} are available in the A
|
||||
|
||||
### Using the {% data variables.product.prodname_ghe_server %} portal to select an AMI
|
||||
|
||||
{% data reusables.enterprise_installation.enterprise-download-procedural %}
|
||||
{% data reusables.enterprise_installation.download-appliance %}
|
||||
3. In the Select your platform drop-down menu, click **Amazon Web Services**.
|
||||
4. In the Select your AWS region drop-down menu, choose your desired region.
|
||||
3. Under "{% data variables.product.prodname_dotcom %} in the Cloud", select the "Select your platform" dropdown menu, and click **Amazon Web Services**.
|
||||
4. Select the "Select your AWS region" drop-down menu, and click your desired region.
|
||||
5. Take note of the AMI ID that is displayed.
|
||||
|
||||
### Using the AWS CLI to select an AMI
|
||||
|
||||
@@ -27,7 +27,6 @@ shortTitle: Install on Hyper-V
|
||||
|
||||
## Downloading the {% data variables.product.prodname_ghe_server %} image
|
||||
|
||||
{% data reusables.enterprise_installation.enterprise-download-procedural %}
|
||||
{% data reusables.enterprise_installation.download-license %}
|
||||
{% data reusables.enterprise_installation.download-appliance %}
|
||||
4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **Hyper-V (VHD)**.
|
||||
|
||||
@@ -26,7 +26,6 @@ shortTitle: Install on OpenStack
|
||||
|
||||
## Downloading the {% data variables.product.prodname_ghe_server %} image
|
||||
|
||||
{% data reusables.enterprise_installation.enterprise-download-procedural %}
|
||||
{% data reusables.enterprise_installation.download-license %}
|
||||
{% data reusables.enterprise_installation.download-appliance %}
|
||||
4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **OpenStack KVM (QCOW2)**.
|
||||
|
||||
@@ -30,7 +30,6 @@ shortTitle: Install on VMware
|
||||
|
||||
## Downloading the {% data variables.product.prodname_ghe_server %} image
|
||||
|
||||
{% data reusables.enterprise_installation.enterprise-download-procedural %}
|
||||
{% data reusables.enterprise_installation.download-license %}
|
||||
{% data reusables.enterprise_installation.download-appliance %}
|
||||
4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **VMware ESXi/vSphere (OVA)**.
|
||||
|
||||
@@ -34,7 +34,6 @@ shortTitle: Install on XenServer
|
||||
|
||||
## Downloading the {% data variables.product.prodname_ghe_server %} image
|
||||
|
||||
{% data reusables.enterprise_installation.enterprise-download-procedural %}
|
||||
{% data reusables.enterprise_installation.download-license %}
|
||||
{% data reusables.enterprise_installation.download-appliance %}
|
||||
4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **XenServer (VHD)**.
|
||||
|
||||
@@ -14,6 +14,8 @@ shortTitle: PAT with SAML
|
||||
---
|
||||
You can authorize an existing personal access token, or [create a new personal access token](/github/authenticating-to-github/creating-a-personal-access-token) and then authorize it.
|
||||
|
||||
{% data reusables.saml.must-authorize-linked-identity %}
|
||||
|
||||
{% data reusables.saml.authorized-creds-info %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
|
||||
@@ -14,6 +14,8 @@ shortTitle: SSH Key with SAML
|
||||
---
|
||||
You can authorize an existing SSH key, or create a new SSH key and then authorize it. For more information about creating a new SSH key, see "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)."
|
||||
|
||||
{% data reusables.saml.must-authorize-linked-identity %}
|
||||
|
||||
{% data reusables.saml.authorized-creds-info %}
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -33,7 +33,7 @@ You must store this file in the `.github` directory of your repository. When you
|
||||
|
||||
Any options that also affect security updates are used the next time a security alert triggers a pull request for a security update. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
|
||||
|
||||
The *dependabot.yml* file has two mandatory top-level keys: `version`, and `updates`. You can, optionally, include a top-level `registries` key. The file must start with `version: 2`.
|
||||
The *dependabot.yml* file has two mandatory top-level keys: `version`, and `updates`. You can, optionally, include a top-level `registries` key{% ifversion fpt or ghec or ghes > 3.4 %} and/or a `enable-beta-ecosystems` key{% endif %}. The file must start with `version: 2`.
|
||||
|
||||
## Configuration options for updates
|
||||
|
||||
@@ -46,7 +46,8 @@ The top-level `updates` key is mandatory. You use it to configure how {% data va
|
||||
| [`schedule.interval`](#scheduleinterval) | **X** | How often to check for updates |
|
||||
| [`allow`](#allow) | | Customize which updates are allowed |
|
||||
| [`assignees`](#assignees) | | Assignees to set on pull requests |
|
||||
| [`commit-message`](#commit-message) | | Commit message preferences |
|
||||
| [`commit-message`](#commit-message) | | Commit message preferences |{% ifversion fpt or ghec or ghes > 3.4 %}
|
||||
| [`enable-beta-ecosystems`](#enable-beta-ecosystems) | | Enable ecosystems that have beta-level support |{% endif %}
|
||||
| [`ignore`](#ignore) | | Ignore certain dependencies or versions |
|
||||
| [`insecure-external-code-execution`](#insecure-external-code-execution) | | Allow or deny code execution in manifest files |
|
||||
| [`labels`](#labels) | | Labels to set on pull requests |
|
||||
@@ -302,7 +303,6 @@ updates:
|
||||
prefix-development: "pip dev"
|
||||
include: "scope"
|
||||
```
|
||||
|
||||
### `ignore`
|
||||
|
||||
{% data reusables.dependabot.default-dependencies-allow-ignore %}
|
||||
@@ -330,7 +330,7 @@ If `versions` and `update-types` are used together, {% data variables.product.pr
|
||||
{% data reusables.dependabot.option-affects-security-updates %}
|
||||
|
||||
```yaml
|
||||
# Use `ignore` to specify dependencies that should not be updated
|
||||
# Use `ignore` to specify dependencies that should not be updated
|
||||
|
||||
version: 2
|
||||
updates:
|
||||
@@ -356,6 +356,15 @@ updates:
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.4 %}
|
||||
{% note %}
|
||||
|
||||
**Note**: For the `pub` ecosystem, {% data variables.product.prodname_dependabot %} won't perform an update when the version that it tries to update to is ignored, even if an earlier version is available.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
### `insecure-external-code-execution`
|
||||
|
||||
Package managers with the `package-ecosystem` values `bundler`, `mix`, and `pip` may execute external code in the manifest as part of the version update process. This might allow a compromised package to steal credentials or gain access to configured registries. When you add a [`registries`](#registries) setting within an `updates` configuration, {% data variables.product.prodname_dependabot %} automatically prevents external code execution, in which case the version update may fail. You can choose to override this behavior and allow external code execution for `bundler`, `mix`, and `pip` package managers by setting `insecure-external-code-execution` to `allow`.
|
||||
@@ -505,7 +514,7 @@ To allow {% data variables.product.prodname_dependabot %} to access a private pa
|
||||
To allow {% data variables.product.prodname_dependabot %} to use `bundler`, `mix`, and `pip` package managers to update dependencies in private registries, you can choose to allow external code execution. For more information, see [`insecure-external-code-execution`](#insecure-external-code-execution) above.
|
||||
|
||||
```yaml
|
||||
# Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries
|
||||
# Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries
|
||||
# when updating dependency versions for this ecosystem
|
||||
|
||||
{% raw %}
|
||||
@@ -723,7 +732,7 @@ updates:
|
||||
|
||||
## Configuration options for private registries
|
||||
|
||||
The top-level `registries` key is optional. It allows you to specify authentication details that {% data variables.product.prodname_dependabot %} can use to access private package registries.
|
||||
The top-level `registries` key is optional. It allows you to specify authentication details that {% data variables.product.prodname_dependabot %} can use to access private package registries.
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -739,7 +748,7 @@ The value of the `registries` key is an associative array, each element of which
|
||||
|
||||
version: 2
|
||||
registries:
|
||||
dockerhub: # Define access for a private registry
|
||||
dockerhub: # Define access for a private registry
|
||||
type: docker-registry
|
||||
url: registry.hub.docker.com
|
||||
username: octocat
|
||||
@@ -769,7 +778,7 @@ You use the following options to specify access settings. Registry settings must
|
||||
|
||||
Each configuration `type` requires you to provide particular settings. Some types allow more than one way to connect. The following sections provide details of the settings you should use for each `type`.
|
||||
|
||||
### `composer-repository`
|
||||
### `composer-repository`
|
||||
|
||||
The `composer-repository` type supports username and password.
|
||||
|
||||
@@ -784,7 +793,7 @@ registries:
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### `docker-registry`
|
||||
### `docker-registry`
|
||||
|
||||
The `docker-registry` type supports username and password.
|
||||
|
||||
@@ -812,7 +821,7 @@ registries:
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### `git`
|
||||
### `git`
|
||||
|
||||
The `git` type supports username and password.
|
||||
|
||||
@@ -827,7 +836,7 @@ registries:
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### `hex-organization`
|
||||
### `hex-organization`
|
||||
|
||||
The `hex-organization` type supports organization and key.
|
||||
|
||||
@@ -883,7 +892,7 @@ registries:
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### `nuget-feed`
|
||||
### `nuget-feed`
|
||||
|
||||
The `nuget-feed` type supports username and password, or token.
|
||||
|
||||
@@ -908,7 +917,7 @@ registries:
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### `python-index`
|
||||
### `python-index`
|
||||
|
||||
The `python-index` type supports username and password, or token.
|
||||
|
||||
@@ -973,3 +982,23 @@ registries:
|
||||
token: ${{secrets.MY_TERRAFORM_API_TOKEN}}
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.4 %}
|
||||
## Enabling support for beta-level ecosystems
|
||||
|
||||
### `enable-beta-ecosystems`
|
||||
|
||||
By default, {% data variables.product.prodname_dependabot %} updates the dependency manifests and lock files only for fully supported ecosystems. Use the `enable-beta-ecosystems` flag to opt in to updates for ecosystems that are not yet generally available.
|
||||
|
||||
```yaml
|
||||
# Configure beta ecosystem
|
||||
|
||||
version: 2
|
||||
enable-beta-ecosystems: true
|
||||
updates:
|
||||
- package-ecosystem: "pub"
|
||||
directory: "/"
|
||||
schedule:
|
||||
interval: "daily"
|
||||
```
|
||||
{% endif %}
|
||||
@@ -56,6 +56,8 @@ If you need to allow external access to services running on a codespace, you can
|
||||
|
||||
If you need to connect to a service (such as a development web server) running within your codespace, you can configure port forwarding to make the service available on the internet.
|
||||
|
||||
Organization owners can restrict the ability to make forward ports available publicly or within the organization. For more information, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)."
|
||||
|
||||
**Privately forwarded ports**: Are accessible on the internet, but only the codespace creator can access them, after authenticating to {% data variables.product.product_name %}.
|
||||
|
||||
**Publicly forwarded ports within your organization**: Are accessible on the internet, but only to members of the same organization as the codespace, after authenticating to {% data variables.product.product_name %}.
|
||||
|
||||
@@ -25,6 +25,12 @@ When an application running inside a codespace prints output to the terminal tha
|
||||
|
||||
You can also forward a port manually, label forwarded ports, share forwarded ports with members of your organization, share forwarded ports publicly, and add forwarded ports to the codespace configuration.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data reusables.codespaces.restrict-port-visibility %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Forwarding a port
|
||||
|
||||
You can manually forward a port that wasn't forwarded automatically.
|
||||
@@ -85,12 +91,18 @@ To see details of forwarded ports enter `gh codespace ports` and then choose a c
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You can only make a port private to an organization if your organization uses {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. This feature is not currently available in the beta version of {% data variables.product.prodname_codespaces %}.
|
||||
**Note:** You can only make a port private to an organization if your organization uses {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If you want to share a forwarded port with others, you can either make the port private to your organization or make the port public. After you make a port private to your organization, anyone in the organization with the port's URL can view the running application. After you make a port public, anyone who knows the URL and port number can view the running application without needing to authenticate.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Your choice of port visibility options may be limited by a policy configured for your organization. For more information, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
@@ -105,7 +117,7 @@ If you want to share a forwarded port with others, you can either make the port
|
||||
{% vscode %}
|
||||
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Right click the port you want to share, then click **Make Public**.
|
||||
1. Right click the port that you want to share, select the "Port Visibility" menu, then click **Private to Organization** or **Public**.
|
||||
|
||||
1. To the right of the local address for the port, click the copy icon.
|
||||
|
||||
|
||||
@@ -41,7 +41,7 @@ Once your codespace is created, your repository will be automatically cloned int
|
||||
|
||||
If you're following along with a different application type, enter the corresponding start command for that project.
|
||||
|
||||
2. When your application starts, the codespace recognizes the port the application is running on and displays a prompt to forward that port so you can connect to it.
|
||||
2. When your application starts, the codespace recognizes the port the application is running on and displays a prompt to let you know it has been forwarded.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -14,6 +14,7 @@ children:
|
||||
- /managing-repository-access-for-your-organizations-codespaces
|
||||
- /reviewing-your-organizations-audit-logs-for-codespaces
|
||||
- /restricting-access-to-machine-types
|
||||
- /restricting-the-visibility-of-forwarded-ports
|
||||
shortTitle: Managing your organization
|
||||
---
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ As an organization owner, you may want to configure constraints on the types of
|
||||
|
||||
### Behavior when you set a machine type constraint
|
||||
|
||||
If there are existing codespaces that no longer conform to a policy you have defined, these codespaces will continue to operate until they time out. When the user attempts to resume the codespace they are shown a message telling them that the currenly selected machine type is no longer allowed for this organization and prompting them to choose an alternative machine type.
|
||||
If there are existing codespaces that no longer conform to a policy you have defined, these codespaces will continue to operate until they are stopped or time out. When the user attempts to resume the codespace they are shown a message telling them that the currenly selected machine type is no longer allowed for this organization and prompting them to choose an alternative machine type.
|
||||
|
||||
If you remove higher specification machine types that are required by the {% data variables.product.prodname_codespaces %} configuration for an individual repository in your organization, then it won't be possible to create a codespace for that repository. When someone attempts to create a codespace they will see a message telling them that there are no valid machine types available that meet the requirements of the repository's {% data variables.product.prodname_codespaces %} configuration.
|
||||
|
||||
|
||||
@@ -0,0 +1,83 @@
|
||||
---
|
||||
title: Restricting the visibility of forwarded ports
|
||||
shortTitle: Restricting port visibility
|
||||
intro: 'You can set constraints on the visibility options users can choose when they forward ports from codespaces in your organization.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an organization owner.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Codespaces
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Typically, within a codespace you are able to forward ports privately (only to yourself), to members of your organization, or publicly (to anyone with the URL). For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
|
||||
|
||||
As an organization owner, you may want to configure constraints on the visibility options users can set when forwarding ports. For example, for security reasons, you may want to disallow public port forwarding. You do this by defining one or more policies in the {% data variables.product.prodname_codespaces %} settings for your organization.
|
||||
|
||||
### Behavior when you set a port visibility constraint
|
||||
|
||||
If there are existing codespaces that no longer conform to a policy you have defined, these codespaces will continue to operate until they are stopped or time out. When the user resumes the codespace, it will be subject to the policy constraints.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: You can't disable private port forwarding, as private port forwarding is required by {% data variables.product.prodname_codespaces %} to continue working as designed, for example to forward SSH on port 22.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Setting organization-wide and repository-specific policies
|
||||
|
||||
When you create a policy you choose whether it applies to all repositories in your organization, or only to specified repositories. If you set an organization-wide policy then any policies you set for individual repositories must fall within the restriction set at the organization level. Adding policies makes the choice of visibility options more, not less, restrictive.
|
||||
|
||||
For example, you could create an organization-wide policy that restricts the visibility options to organization only. You can then set a policy for Repository A that disallows both public and organization visibility, which would result in only private port forwarding being available for this repository. Setting a policy for Repository A that allowed both public and organization would result in only organization visibility, because the organization-wide policy does not allow public visibility.
|
||||
|
||||
If you add an organization-wide policy, you should set it to the most lenient visibility option that will be available for any repository in your organization. You can then add repository-specific policies to further restrict the choice.
|
||||
|
||||
## Adding a policy to limit the port visibility options
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policies**.
|
||||
1. On the "Codespace policies" page, click **Create Policy**.
|
||||
1. Enter a name for your new policy.
|
||||
1. Click **Add constraint** and choose **Port visibility**.
|
||||
|
||||
|
||||
|
||||
1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint
|
||||
|
||||
|
||||
|
||||
1. Clear the selection of the port visibility options (**Org** or **Public**) that you don't want to be available.
|
||||
|
||||
|
||||
|
||||
1. In the "Change policy target" area, click the dropdown button.
|
||||
1. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to.
|
||||
1. If you chose **Selected repositories**:
|
||||
1. Click {% octicon "gear" aria-label="The settings icon" %}.
|
||||
|
||||
|
||||
|
||||
2. Select the repositories you want this policy to apply to.
|
||||
3. At the bottom of the repository list, click **Select repositories**.
|
||||
|
||||
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
## Editing a policy
|
||||
|
||||
1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the port visibility options](#adding-a-policy-to-limit-the-port-visibility-options)."
|
||||
1. Click the name of the policy you want to edit.
|
||||
1. Make the required changes then click **Save**.
|
||||
|
||||
## Deleting a policy
|
||||
|
||||
1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the port visibility options](#adding-a-policy-to-limit-the-port-visibility-options)."
|
||||
1. Click the delete button to the right of the policy you want to delete.
|
||||
|
||||
|
||||
@@ -19,3 +19,5 @@ If port forwarding is set up, check the following:
|
||||
|
||||
- Use the notification toast or click the URL in Terminal to open the forwarded port. Typing in `localhost:8000` (as an example) to your local machine will not work if you're connected to the codespace via the browser.
|
||||
- Make sure to check that your application is still running from within your codespace. If your codespace has stopped after a period of inactivity, you'll need to ensure to restart your application once the codespace has restarted.
|
||||
|
||||
Typically, you can make a forwarded port accessible publicly, or within the organization that owns a repository. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." If either, or both, of the options for public or organization visibility are not available, this indicates that an organization-level policy has been configured. For more information, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)."
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Blocking a user from your organization
|
||||
intro: Organization owners can block a user to remove the user's ability to collaborate in the organization's repositories.
|
||||
intro: Organization owners and moderators can block anyone who is not a member of the organization from collaborating on the organization's repositories.
|
||||
redirect_from:
|
||||
- /articles/blocking-a-user-from-your-organization
|
||||
- /github/building-a-strong-community/blocking-a-user-from-your-organization
|
||||
@@ -12,7 +12,7 @@ topics:
|
||||
shortTitle: Block from your org
|
||||
---
|
||||
|
||||
You can block a user from within your organization's settings or from a specific comment made by the user. When you block a user in a comment, you can choose to send the user a notification explaining that they were blocked and why. Otherwise, the user is not directly notified that you've blocked them. Blocked users can still delete their existing content.
|
||||
You can block non-members from within your organization's settings or from a specific comment made by a user. When you block a user in a comment, you can choose to send the user a notification explaining that they were blocked and why. Otherwise, the user is not directly notified that you've blocked them. Blocked users can still delete their existing content.
|
||||
|
||||
When you block a user, you can choose to block them indefinitely or for a specific amount of time. If you block someone for a specific amount of time, they are automatically unblocked after the chosen time expires. If you block someone indefinitely, you can unblock them manually at any time. For more information, see "[Unblocking a user from your organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)."
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Unblocking a user from your organization
|
||||
intro: 'Organization owners can unblock a user who was previously blocked, restoring their access to the organization''s repositories.'
|
||||
intro: 'Organization owners and moderators can unblock a user who was previously blocked, restoring their access to the organization''s repositories.'
|
||||
redirect_from:
|
||||
- /articles/unblocking-a-user-from-your-organization
|
||||
- /github/building-a-strong-community/unblocking-a-user-from-your-organization
|
||||
@@ -27,15 +27,15 @@ If you selected a specific amount of time to block the user, they will be automa
|
||||
1. Navigate to the comment whose author you would like to unblock.
|
||||
2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Unblock user**.
|
||||
|
||||
3. To confirm you would like to unblock the user, click **Okay**.
|
||||
3. To confirm you would like to unblock the user, click **OK**.
|
||||
|
||||
## Unblocking a user in the organization settings
|
||||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.moderation-settings %}, then click **Blocked users**.
|
||||
5. Under "Blocked users", next to the user you'd like to unblock, click **Unblock**.
|
||||
{% data reusables.organizations.block_users %}
|
||||
1. Under "Blocked users", next to the user you'd like to unblock, click **Unblock**.
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
@@ -8,7 +8,7 @@ redirect_from:
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
permissions: Organization owners can limit interactions in an organization.
|
||||
permissions: Organization owners and moderators can limit interactions in an organization.
|
||||
topics:
|
||||
- Community
|
||||
shortTitle: Limit interactions in org
|
||||
@@ -26,14 +26,17 @@ Members of the organization are not affected by any of the limit types.
|
||||
|
||||
When you enable organization-wide activity limitations, you can't enable or disable interaction limits on individual repositories. For more information on limiting activity for an individual repository, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
|
||||
|
||||
Organization owners can also block users for a specific amount of time. After the block expires, the user is automatically unblocked. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."
|
||||
Organization owners and moderators can also block users for a specific amount of time. After the block expires, the user is automatically unblocked. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."
|
||||
|
||||
## Limiting interactions in your organization
|
||||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Interaction limits**.
|
||||
1. _For organization owners:_ In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Interaction limits**.
|
||||
|
||||
_For organization moderators:_ In the sidebar, click **Interaction limits**.
|
||||
|
||||
{% data reusables.community.set-interaction-limit %}
|
||||
|
||||
|
||||
@@ -42,3 +45,4 @@ Organization owners can also block users for a specific amount of time. After th
|
||||
- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
|
||||
- "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository)"
|
||||
- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
|
||||
- "[Managing moderators in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization)"
|
||||
@@ -8,7 +8,7 @@ redirect_from:
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
permissions: People with admin permissions to a repository can temporarily limit interactions in that repository.
|
||||
permissions: People with admin permissions to a repository, and organization moderators, can temporarily limit interactions in that repository.
|
||||
topics:
|
||||
- Community
|
||||
shortTitle: Limit interactions in repo
|
||||
@@ -28,7 +28,7 @@ You can also enable activity limitations on all repositories owned by your user
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
1. In the "Access" section of the sidebar, select **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Moderation options**, then click **Interaction limits**.
|
||||
1. In the sidebar, select **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Moderation options**, then click **Interaction limits**.
|
||||
{% data reusables.community.set-interaction-limit %}
|
||||
|
||||
|
||||
@@ -37,3 +37,4 @@ You can also enable activity limitations on all repositories owned by your user
|
||||
- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
|
||||
- "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository)"
|
||||
- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
|
||||
- "[Managing moderators in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization)"
|
||||
@@ -18,7 +18,7 @@ shortTitle: Manage comments
|
||||
|
||||
## Hiding a comment
|
||||
|
||||
Anyone with write access to a repository can hide comments on issues, pull requests, and commits.
|
||||
{% ifversion fpt or ghec %}Organization moderators, and anyone{% else %}Anyone{% endif %} with write access to a repository, can hide comments on issues, pull requests, and commits.
|
||||
|
||||
If a comment is off-topic, outdated, or resolved, you may want to hide a comment to keep a discussion focused or make a pull request easier to navigate and review. Hidden comments are minimized but people with read access to the repository can expand them.
|
||||
|
||||
@@ -36,7 +36,7 @@ If a comment is off-topic, outdated, or resolved, you may want to hide a comment
|
||||
|
||||
## Unhiding a comment
|
||||
|
||||
Anyone with write access to a repository can unhide comments on issues, pull requests, and commits.
|
||||
{% ifversion fpt or ghec %}Organization moderators, and anyone{% else %}Anyone{% endif %} with write access to a repository, can unhide comments on issues, pull requests, and commits.
|
||||
|
||||
1. Navigate to the comment you'd like to unhide.
|
||||
2. In the upper-right corner of the comment, click **{% octicon "fold" aria-label="The fold icon" %} Show comment**.
|
||||
@@ -89,3 +89,8 @@ If a comment contains some constructive content that adds to the conversation in
|
||||
2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**.
|
||||
|
||||
3. Optionally, write a comment noting that you deleted a comment and why.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## Further reading
|
||||
- "[Managing moderators in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization)"
|
||||
{% endif %}
|
||||
|
||||
@@ -17,6 +17,8 @@ shortTitle: Management & moderation
|
||||
|
||||
{% data variables.product.prodname_dotcom %} also offers tools for repository maintainers to define and enforce higher standards of behavior in their own communities on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
Organization owners can specify organization members as moderators. This gives these members access to moderation features otherwise reserved for organization owners. For more information, see "[Managing moderators in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization)."
|
||||
|
||||
After you establish standards of behavior for your community, you can encourage a pleasant and productive environment by responding to disruptive behavior in a fast, fair way. Effective moderation builds trust within your community and helps contributors feel safe and welcome.
|
||||
|
||||
## Tools for moderating your community
|
||||
|
||||
@@ -189,6 +189,12 @@ To create a nested list using the web editor on {% data variables.product.produc
|
||||
- Second nested list item
|
||||
```
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Note**: In the web-based editor, you can indent or dedent one or more lines of text by first highlighting the desired lines and then using <kbd>Tab</kbd> or <kbd>Shift</kbd>+<kbd>Tab</kbd> respectively.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ shortTitle: Access organization settings
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** Only organization owners and billing managers can see and change the billing information and account settings for an organization. {% data reusables.organizations.new-org-permissions-more-info %}
|
||||
**Tip:** Only organization owners and billing managers can see and change the billing information and the full set of account settings for an organization. Organization moderators only see moderation settings. {% data reusables.organizations.new-org-permissions-more-info %}
|
||||
|
||||
{% endtip %}
|
||||
|
||||
|
||||
@@ -41,9 +41,9 @@ To search for specific events, use the `action` qualifier in your query. Actions
|
||||
| [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
|
||||
| [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing.
|
||||
| [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. |
|
||||
| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
|
||||
| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
|
||||
| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.
|
||||
| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %}
|
||||
| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
|
||||
| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
|
||||
| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
|
||||
| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.{% endif %}{% ifversion fpt or ghec %}
|
||||
| [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
|
||||
@@ -63,8 +63,8 @@ To search for specific events, use the `action` qualifier in your query. Actions
|
||||
| [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if secret-scanning-audit-log-custom-patterns %}
|
||||
| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae or ghec %}
|
||||
| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %}
|
||||
| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps.{% ifversion fpt or ghes or ghec %}
|
||||
| [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% endif %}{% ifversion fpt or ghec %}
|
||||
| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps.
|
||||
| [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% ifversion fpt or ghec %}
|
||||
| [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %}
|
||||
| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture.
|
||||
| [`project`](#project-category-actions) | Contains all activities related to project boards.
|
||||
@@ -236,7 +236,7 @@ An overview of some of the most common actions that are recorded as events in th
|
||||
| `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.2 %}
|
||||
{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %}
|
||||
### `dependabot_alerts` category actions
|
||||
|
||||
| Action | Description
|
||||
@@ -250,7 +250,9 @@ An overview of some of the most common actions that are recorded as events in th
|
||||
|------------------|-------------------
|
||||
| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
|
||||
| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.2 %}
|
||||
### `dependabot_security_updates` category actions
|
||||
|
||||
| Action | Description
|
||||
@@ -516,18 +518,15 @@ For more information, see "[Managing the publication of {% data variables.produc
|
||||
| `revoke_tokens` | Triggered when an {% data variables.product.prodname_oauth_app %}'s user tokens are revoked.
|
||||
| `transfer` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is transferred to a new organization.
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
### `packages` category actions
|
||||
|
||||
| Action | Description |
|
||||
|--------|-------------|
|
||||
| `package_version_published` | Triggered when a package version is published. |
|
||||
| `package_version_deleted` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
| `package_deleted` | Triggered when an entire package is deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
| `package_version_restored` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
| `package_restored` | Triggered when an entire package is restored.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
|
||||
{% endif %}
|
||||
| `package_version_deleted` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
| `package_deleted` | Triggered when an entire package is deleted.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
| `package_version_restored` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
| `package_restored` | Triggered when an entire package is restored.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ You can also enable code review limits for individual repositories. If you enabl
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.moderation-settings %}
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "report" aria-label="The report icon" %} Moderation**.
|
||||
1. Under "{% octicon "report" aria-label="The report icon" %} Moderation", click **Code review limits**.
|
||||
|
||||
1. Review the information on screen. Click **Limit review on all repositories** to limit reviews to those with explicit access, or click **Remove review limits from all repositories** to remove the limits from every public repository in your organization.
|
||||
|
||||
@@ -20,6 +20,7 @@ children:
|
||||
- /adding-a-billing-manager-to-your-organization
|
||||
- /removing-a-billing-manager-from-your-organization
|
||||
- /managing-security-managers-in-your-organization
|
||||
- /managing-moderators-in-your-organization
|
||||
shortTitle: Manage access with roles
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: Managing moderators in your organization
|
||||
intro: You can give an individual or team in your organization the ability to block and limit access, by assigning them to the moderator role.
|
||||
permissions: Organization owners can assign the moderator role.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Organizations
|
||||
- Teams
|
||||
- Community
|
||||
shortTitle: Managing moderators
|
||||
---
|
||||
|
||||
## About organization moderators
|
||||
|
||||
Sometimes it's necessary to block a contributor, or to set up interaction limits for your organization, or for individual repositories. As an organization owner, you can perform these tasks, but you may want to delegate these tasks to other members of your organization. You can do this by assigning an organization member, or a team, to the moderator role.
|
||||
|
||||
Organization moderators can:
|
||||
* Block and unblock users from the organization. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."
|
||||
* Manage organization interaction limits. For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)."
|
||||
* Manage repository interaction limits. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
|
||||
* Hide comments in all public repositories owned by the organization. For more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)."
|
||||
|
||||
Making someone an organization moderator does not give them additional abilities other than those listed above. For example, someone who only has read access to a repository will not gain write access by being made a moderator.
|
||||
|
||||
You can add up to 10 individual people, or teams, as moderators. If you've already assigned 10 individuals and/or teams as users and you want to add more, you can group people in a moderators team and then use this to replace one or more of the existing assignments. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)."
|
||||
|
||||
## Adding an organization moderator
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security-and-analysis %}
|
||||
1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Moderators**.
|
||||
1. Under **Moderators**, search for and select the person or team you want to assign the moderator role. Each person or team you select will appear in a list below the search bar.
|
||||
|
||||
|
||||
|
||||
## Removing an organization moderator
|
||||
|
||||
Follow steps 1-4 above, then click **Remove moderator** beside the person or team you want to remove as a moderator.
|
||||
@@ -40,6 +40,9 @@ Organization owners have complete administrative access to your organization. Th
|
||||
The default, non-administrative role for people in an organization is the organization member. By default, organization members have a number of permissions, including the ability to create repositories and project boards.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### Organization moderators
|
||||
Moderators are organization members who, in addition to their permissions as members, are allowed to block and unblock non-member contributors, set interaction limits, and hide comments in public repositories owned by the organization. For more information, see "[Managing moderators in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization)."
|
||||
|
||||
### Billing managers
|
||||
Billing managers are users who can manage the billing settings for your organization, such as payment information. This is a useful option if members of your organization don't usually have access to billing resources. For more information, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."
|
||||
|
||||
@@ -72,69 +75,72 @@ Some of the features listed below are limited to organizations using {% data var
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
<!--Dotcom and cloud version has extra column for Billing managers-->
|
||||
<!-- Free/Pro/Team and GHEC versions have extra columns for Moderators and Billing managers-->
|
||||
|
||||
| Organization permission | Owners | Members | Billing managers | Security managers |
|
||||
|:--------------------|:------:|:-------:|:----------------:|:----------------:|
|
||||
| Create repositories (see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)" for details) | **X** | **X** | | **X** |
|
||||
| View and edit billing information | **X** | | **X** | |
|
||||
| Invite people to join the organization | **X** | | | |
|
||||
| Edit and cancel invitations to join the organization | **X** | | | |
|
||||
| Remove members from the organization | **X** | | | |
|
||||
| Reinstate former members to the organization | **X** | | | |
|
||||
| Add and remove people from **all teams** | **X** | | | |
|
||||
| Promote organization members to *team maintainer* | **X** | | | |
|
||||
| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | |
|
||||
| Set scheduled reminders (see "[Managing scheduled reminders for pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | |
|
||||
| Add collaborators to **all repositories** | **X** | | | |
|
||||
| Access the organization audit log | **X** | | | |
|
||||
| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" for details) | **X** | | | |
|
||||
| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)" for details) | **X** | | | |
|
||||
| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details) | **X** | | | |
|
||||
| Delete **all teams** | **X** | | | |
|
||||
| Delete the organization account, including all repositories | **X** | | | |
|
||||
| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)" for details) | **X** | **X** | | **X** |
|
||||
| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | |
|
||||
| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | | **X** |
|
||||
| See all organization members and teams | **X** | **X** | | **X** |
|
||||
| @mention any visible team | **X** | **X** | | **X** |
|
||||
| Can be made a *team maintainer* | **X** | **X** | | **X** |
|
||||
| View organization insights (see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization)" for details) | **X** | **X** | | **X** |
|
||||
| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | | **X** |
|
||||
| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | | | |
|
||||
| Edit and delete team discussions in **all teams** (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)" for details) | **X** | | | |
|
||||
| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | | **X** |
|
||||
| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details) | **X** | | | |
|
||||
| Manage viewing of organization dependency insights (see "[Changing the visibility of your organization's dependency insights](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" for details) | **X** | | | |
|
||||
| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)" for details) | **X** | | | |
|
||||
| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/sponsors/sponsoring-open-source-contributors)" for details) | **X** | | **X** | **X** |
|
||||
| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | |
|
||||
| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)" for details ) | **X** | | | |
|
||||
| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | | |
|
||||
| Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" for details) | **X** | | | **X** |
|
||||
| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | | **X** |{% ifversion ghec %}
|
||||
| Enable and enforce [SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | |
|
||||
| [Manage a user's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | |
|
||||
| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** | | | |{% endif %}
|
||||
| Transfer repositories | **X** | | | |
|
||||
| Purchase, install, manage billing for, and cancel {% data variables.product.prodname_marketplace %} apps | **X** | | | |
|
||||
| List apps in {% data variables.product.prodname_marketplace %} | **X** | | | |
|
||||
| Receive [{% data variables.product.prodname_dependabot_alerts %} about vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) for all of an organization's repositories | **X** | | | **X** |
|
||||
| Manage {% data variables.product.prodname_dependabot_security_updates %} (see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | | **X** |
|
||||
| [Manage the forking policy](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** | | |
|
||||
| [Limit activity in public repositories in an organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | | |
|
||||
| Pull (read) *all repositories* in the organization | **X** | | | **X** |
|
||||
| Push (write) and clone (copy) *all repositories* in the organization | **X** | | | |
|
||||
| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | | | |
|
||||
| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | | | |{% ifversion ghec or ghes or ghae %}
|
||||
| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | |{% endif %}
|
||||
| Manage the default branch name (see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | |
|
||||
| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | |{% ifversion ghec %}
|
||||
| Enable team synchronization (see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" for details) | **X** | | | |{% endif %}
|
||||
| Manage pull request reviews in the organization (see "[Managing pull request reviews in your organization](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)") | **X** | | | |
|
||||
| Organization permission | Owners | Members | Moderators | Billing managers | Security managers |
|
||||
|:------------------------|:------:|:-------:|:----------:|:----------------:|:-----------------:|
|
||||
| Create repositories (see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)") | **X** | **X** | **X** | | **X** |
|
||||
| View and edit billing information | **X** | | | **X** | |
|
||||
| Invite people to join the organization | **X** | | | | |
|
||||
| Edit and cancel invitations to join the organization | **X** | | | | |
|
||||
| Remove members from the organization | **X** | | | | |
|
||||
| Reinstate former members to the organization | **X** | | | | |
|
||||
| Add and remove people from **all teams** | **X** | | | | |
|
||||
| Promote organization members to *team maintainer* | **X** | | | | |
|
||||
| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | | |
|
||||
| Set scheduled reminders (see "[Managing scheduled reminders for pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | | |
|
||||
| Add collaborators to **all repositories** | **X** | | | | |
|
||||
| Access the organization audit log | **X** | | | | |
|
||||
| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)") | **X** | | | | |
|
||||
| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)") | **X** | | | | |
|
||||
| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)") | **X** | | | | |
|
||||
| Delete **all teams** | **X** | | | | |
|
||||
| Delete the organization account, including all repositories | **X** | | | | |
|
||||
| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)") | **X** | **X** | **X** | | **X** |
|
||||
| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | | |
|
||||
| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)") | **X** | **X** | **X** | | **X** |
|
||||
| See all organization members and teams | **X** | **X** | **X** | | **X** |
|
||||
| @mention any visible team | **X** | **X** | **X** | | **X** |
|
||||
| Can be made a *team maintainer* | **X** | **X** | **X** | | **X** |
|
||||
| View organization insights (see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization)") | **X** | **X** | **X** | | **X** |
|
||||
| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | **X** | **X** | | **X** |
|
||||
| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | | | | |
|
||||
| Edit and delete team discussions in **all teams** (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)") | **X** | | | | |
|
||||
| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)") | **X** | | | | |
|
||||
| Hide comments on writable commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)") | **X** | **X** | **X** | | **X** |
|
||||
| Hide comments on _all_ commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)") | **X** | | **X** | | **X** |
|
||||
| Block and unblock non-member contributors (see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)") | **X** | | **X** | | |
|
||||
| Limit interactions for certain users in public repositories (see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)") | **X** | | **X** | | |
|
||||
| Manage viewing of organization dependency insights (see "[Changing the visibility of your organization's dependency insights](/articles/changing-the-visibility-of-your-organizations-dependency-insights)") | **X** | | | | |
|
||||
| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)") | **X** | | | | |
|
||||
| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/sponsors/sponsoring-open-source-contributors)") | **X** | | | **X** | **X** |
|
||||
| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)") | **X** | | | | |
|
||||
| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)" for details ) | **X** | | | | |
|
||||
| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)") | **X** | | | | |
|
||||
| Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | **X** | | | | **X** |
|
||||
| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)") | **X** | | | | **X** |{% ifversion ghec %}
|
||||
| Enable and enforce [SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | | |
|
||||
| [Manage a user's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | | |
|
||||
| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)") | **X** | | | | |{% endif %}
|
||||
| Transfer repositories | **X** | | | | |
|
||||
| Purchase, install, manage billing for, and cancel {% data variables.product.prodname_marketplace %} apps | **X** | | | | |
|
||||
| List apps in {% data variables.product.prodname_marketplace %} | **X** | | | | |
|
||||
| Receive [{% data variables.product.prodname_dependabot_alerts %} about vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) for all of an organization's repositories | **X** | | | | **X** |
|
||||
| Manage {% data variables.product.prodname_dependabot_security_updates %} (see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | | | **X** |
|
||||
| [Manage the forking policy](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** | | | | |
|
||||
| [Limit activity in public repositories in an organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | | | |
|
||||
| Pull (read) *all repositories* in the organization | **X** | | | | **X** |
|
||||
| Push (write) and clone (copy) *all repositories* in the organization | **X** | | | | |
|
||||
| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | | | | |
|
||||
| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | | | | |{% ifversion ghec %}
|
||||
| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | | |{% endif %}
|
||||
| Manage the default branch name (see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | | |
|
||||
| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | | |{% ifversion ghec %}
|
||||
| Enable team synchronization (see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)") | **X** | | | | |{% endif %}
|
||||
| Manage pull request reviews in the organization (see "[Managing pull request reviews in your organization](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)") | **X** | | | | |
|
||||
|
||||
{% elsif ghes > 3.2 or ghae-issue-4999 %}
|
||||
<!--GHES 3.3+ and eventual GHAE release don't have the extra column for Billing managers, but have security managers-->
|
||||
<!-- GHES 3.3+ and eventual GHAE release don't have the extra columns for Moderators and Billing managers. -->
|
||||
|
||||
| Organization action | Owners | Members | Security managers |
|
||||
|:--------------------|:------:|:-------:|:-------:|
|
||||
@@ -147,28 +153,28 @@ Some of the features listed below are limited to organizations using {% data var
|
||||
| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | |
|
||||
| Add collaborators to **all repositories** | **X** | | |
|
||||
| Access the organization audit log | **X** | | |
|
||||
| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" for details) | **X** | | |{% ifversion ghes > 3.1 %}
|
||||
| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)" for details) | **X** | | |
|
||||
| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details) | **X** | | |{% endif %}
|
||||
| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)") | **X** | | |{% ifversion ghes > 3.1 %}
|
||||
| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)") | **X** | | |
|
||||
| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)") | **X** | | |{% endif %}
|
||||
| Delete **all teams** | **X** | | |
|
||||
| Delete the organization account, including all repositories | **X** | | |
|
||||
| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)" for details) | **X** | **X** | **X** |
|
||||
| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)") | **X** | **X** | **X** |
|
||||
| See all organization members and teams | **X** | **X** | **X** |
|
||||
| @mention any visible team | **X** | **X** | **X** |
|
||||
| Can be made a *team maintainer* | **X** | **X** | **X** |
|
||||
| Transfer repositories | **X** | | |
|
||||
| Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" for details) | **X** | | **X** |{% ifversion ghes > 3.1 %}
|
||||
| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | **X** |{% endif %}{% ifversion ghes > 3.2 %}
|
||||
| Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | **X** | | **X** |{% ifversion ghes > 3.1 %}
|
||||
| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)") | **X** | | **X** |{% endif %}{% ifversion ghes > 3.2 %}
|
||||
| Manage {% data variables.product.prodname_dependabot_security_updates %} (see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | **X** |{% endif %}
|
||||
| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** | | |
|
||||
| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | **X** |
|
||||
| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | **X** |
|
||||
| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | | |
|
||||
| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)") | **X** | | |
|
||||
| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)") | **X** | **X** | **X** |
|
||||
| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | **X** | **X** |
|
||||
| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | | |
|
||||
| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | |
|
||||
| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | **X** |
|
||||
| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details) | **X** | | |
|
||||
| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)" for details) | **X** | | |{% ifversion ghes > 3.0 %}
|
||||
| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | |{% endif %}
|
||||
| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)") | **X** | **X** | **X** |
|
||||
| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)") | **X** | | |
|
||||
| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)") | **X** | | |{% ifversion ghes > 3.0 %}
|
||||
| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)") | **X** | | |{% endif %}
|
||||
| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | |
|
||||
| Pull (read) *all repositories* in the organization | **X** | | **X** |
|
||||
| Push (write) and clone (copy) *all repositories* in the organization | **X** | | |
|
||||
@@ -181,7 +187,7 @@ Some of the features listed below are limited to organizations using {% data var
|
||||
|
||||
|
||||
{% else %}
|
||||
<!--GHES and GHAE older versions don't have the extra column for Billing managers or Security managers-->
|
||||
<!-- GHES and GHAE older versions don't have columns for Moderators, Billing managers or Security managers. -->
|
||||
|
||||
| Organization action | Owners | Members |
|
||||
|:--------------------|:------:|:-------:|
|
||||
@@ -194,25 +200,25 @@ Some of the features listed below are limited to organizations using {% data var
|
||||
| Configure code review assignments (see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)")) | **X** | |
|
||||
| Add collaborators to **all repositories** | **X** | |
|
||||
| Access the organization audit log | **X** | |
|
||||
| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" for details) | **X** | | |{% ifversion ghes > 3.1 %}
|
||||
| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)" for details) | **X** | |
|
||||
| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details) | **X** | |{% endif %}
|
||||
| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)") | **X** | | |{% ifversion ghes > 3.1 %}
|
||||
| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)") | **X** | |
|
||||
| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)") | **X** | |{% endif %}
|
||||
| Delete **all teams** | **X** | |
|
||||
| Delete the organization account, including all repositories | **X** | |
|
||||
| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)" for details) | **X** | **X** |
|
||||
| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)") | **X** | **X** |
|
||||
| See all organization members and teams | **X** | **X** |
|
||||
| @mention any visible team | **X** | **X** |
|
||||
| Can be made a *team maintainer* | **X** | **X** |
|
||||
| Transfer repositories | **X** | |
|
||||
| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** | |
|
||||
| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | |
|
||||
| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | |
|
||||
| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | | |
|
||||
| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)") | **X** | |
|
||||
| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)") | **X** | **X** | |
|
||||
| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | **X** | |
|
||||
| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | | |
|
||||
| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | |
|
||||
| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | **X** |
|
||||
| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details) | **X** | | |
|
||||
| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)" for details) | **X** | | |{% ifversion ghes > 3.0 %}
|
||||
| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | |{% endif %}
|
||||
| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)") | **X** | **X** | **X** |
|
||||
| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)") | **X** | | |
|
||||
| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)") | **X** | | |{% ifversion ghes > 3.0 %}
|
||||
| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)") | **X** | |{% endif %}
|
||||
| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | |
|
||||
| Pull (read), push (write), and clone (copy) *all repositories* in the organization | **X** | |
|
||||
| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | |
|
||||
|
||||
@@ -61,7 +61,7 @@ You can view the merge queue for a base branch in various places on {% data vari
|
||||
|
||||
|
||||
|
||||
- On the pull request page when merge queue is required for merging, scroll to the bottom of the timeline and click **the merge queue** link.
|
||||
- On the pull request page when merge queue is required for merging, scroll to the bottom of the timeline and click the **merge queue** link.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -16,10 +16,14 @@ shortTitle: Social media preview
|
||||
---
|
||||
Until you add an image, repository links expand to show basic information about the repository and the owner's avatar. Adding an image to your repository can help identify your project across various social platforms.
|
||||
|
||||
## Adding an image to customize the social media preview of your repository
|
||||
|
||||
{% ifversion not ghae %}You can upload an image to a private repository, but your image can only be shared from a public repository.{% endif %}
|
||||
|
||||
{% tip %}
|
||||
Tip: Your image should be a PNG, JPG, or GIF file under 1 MB in size. For the best quality rendering, we recommend keeping the image at 640 by 320 pixels.
|
||||
|
||||
**Tip:** Your image should be a PNG, JPG, or GIF file under 1 MB in size. For the best quality rendering, we recommend keeping the image at 640 by 320 pixels.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
@@ -29,3 +33,16 @@ Tip: Your image should be a PNG, JPG, or GIF file under 1 MB in size. For the be
|
||||
- To remove an image, click **Remove image**
|
||||
|
||||
|
||||
|
||||
## About transparency
|
||||
|
||||
We support PNG images with transparency. Many communication platforms support a dark mode, so using a transparent social preview may be beneficial. The transparent image below is acceptable on a dark background; however, this may not always be the case.
|
||||
|
||||
When using an image with transparency, keep in mind how it may look on different color backgrounds or platforms that don't support transparency.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** If you aren't sure, we recommend using an image with a solid background.
|
||||
{% endtip %}
|
||||
|
||||
|
||||
|
||||
@@ -1560,6 +1560,11 @@ type BranchProtectionRule implements Node {
|
||||
"""
|
||||
allowsForcePushes: Boolean!
|
||||
|
||||
"""
|
||||
Is branch creation a protected operation.
|
||||
"""
|
||||
blocksCreations: Boolean!
|
||||
|
||||
"""
|
||||
A list of conflicts matching branches protection rule and other branch protection rules
|
||||
"""
|
||||
@@ -5327,6 +5332,11 @@ input CreateBranchProtectionRuleInput {
|
||||
"""
|
||||
allowsForcePushes: Boolean
|
||||
|
||||
"""
|
||||
Is branch creation a protected operation.
|
||||
"""
|
||||
blocksCreations: Boolean
|
||||
|
||||
"""
|
||||
A list of User or Team IDs allowed to bypass force push targeting matching branches.
|
||||
"""
|
||||
@@ -28202,6 +28212,11 @@ type RefUpdateRule {
|
||||
"""
|
||||
allowsForcePushes: Boolean!
|
||||
|
||||
"""
|
||||
Can matching branches be created.
|
||||
"""
|
||||
blocksCreations: Boolean!
|
||||
|
||||
"""
|
||||
Identifies the protection rule pattern.
|
||||
"""
|
||||
@@ -39047,6 +39062,11 @@ input UpdateBranchProtectionRuleInput {
|
||||
"""
|
||||
allowsForcePushes: Boolean
|
||||
|
||||
"""
|
||||
Is branch creation a protected operation.
|
||||
"""
|
||||
blocksCreations: Boolean
|
||||
|
||||
"""
|
||||
The global relay id of the branch protection rule to be updated.
|
||||
"""
|
||||
|
||||
@@ -1716,6 +1716,11 @@ type BranchProtectionRule implements Node {
|
||||
"""
|
||||
allowsForcePushes: Boolean!
|
||||
|
||||
"""
|
||||
Is branch creation a protected operation.
|
||||
"""
|
||||
blocksCreations: Boolean!
|
||||
|
||||
"""
|
||||
A list of conflicts matching branches protection rule and other branch protection rules
|
||||
"""
|
||||
@@ -5565,6 +5570,11 @@ input CreateBranchProtectionRuleInput {
|
||||
"""
|
||||
allowsForcePushes: Boolean
|
||||
|
||||
"""
|
||||
Is branch creation a protected operation.
|
||||
"""
|
||||
blocksCreations: Boolean
|
||||
|
||||
"""
|
||||
A list of User or Team IDs allowed to bypass force push targeting matching branches.
|
||||
"""
|
||||
@@ -32266,6 +32276,11 @@ type RefUpdateRule {
|
||||
"""
|
||||
allowsForcePushes: Boolean!
|
||||
|
||||
"""
|
||||
Can matching branches be created.
|
||||
"""
|
||||
blocksCreations: Boolean!
|
||||
|
||||
"""
|
||||
Identifies the protection rule pattern.
|
||||
"""
|
||||
@@ -44975,6 +44990,11 @@ input UpdateBranchProtectionRuleInput {
|
||||
"""
|
||||
allowsForcePushes: Boolean
|
||||
|
||||
"""
|
||||
Is branch creation a protected operation.
|
||||
"""
|
||||
blocksCreations: Boolean
|
||||
|
||||
"""
|
||||
The global relay id of the branch protection rule to be updated.
|
||||
"""
|
||||
|
||||
@@ -1716,6 +1716,11 @@ type BranchProtectionRule implements Node {
|
||||
"""
|
||||
allowsForcePushes: Boolean!
|
||||
|
||||
"""
|
||||
Is branch creation a protected operation.
|
||||
"""
|
||||
blocksCreations: Boolean!
|
||||
|
||||
"""
|
||||
A list of conflicts matching branches protection rule and other branch protection rules
|
||||
"""
|
||||
@@ -5565,6 +5570,11 @@ input CreateBranchProtectionRuleInput {
|
||||
"""
|
||||
allowsForcePushes: Boolean
|
||||
|
||||
"""
|
||||
Is branch creation a protected operation.
|
||||
"""
|
||||
blocksCreations: Boolean
|
||||
|
||||
"""
|
||||
A list of User or Team IDs allowed to bypass force push targeting matching branches.
|
||||
"""
|
||||
@@ -32266,6 +32276,11 @@ type RefUpdateRule {
|
||||
"""
|
||||
allowsForcePushes: Boolean!
|
||||
|
||||
"""
|
||||
Can matching branches be created.
|
||||
"""
|
||||
blocksCreations: Boolean!
|
||||
|
||||
"""
|
||||
Identifies the protection rule pattern.
|
||||
"""
|
||||
@@ -44975,6 +44990,11 @@ input UpdateBranchProtectionRuleInput {
|
||||
"""
|
||||
allowsForcePushes: Boolean
|
||||
|
||||
"""
|
||||
Is branch creation a protected operation.
|
||||
"""
|
||||
blocksCreations: Boolean
|
||||
|
||||
"""
|
||||
The global relay id of the branch protection rule to be updated.
|
||||
"""
|
||||
|
||||
41
data/release-notes/enterprise-server/3-1/19.yml
Normal file
41
data/release-notes/enterprise-server/3-1/19.yml
Normal file
@@ -0,0 +1,41 @@
|
||||
date: '2022-04-04'
|
||||
sections:
|
||||
security_fixes:
|
||||
- 'MEDIUM: A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} Management Console that allowed the bypass of CSRF protections. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.5 and was fixed in versions 3.1.19, 3.2.11, 3.3.6, 3.4.1. This vulnerability was reported via the {% data variables.product.prodname_dotcom %} Bug Bounty program and has been assigned CVE-2022-23732.'
|
||||
- 'MEDIUM: An integer overflow vulnerability was identified in the 1.x branch and the 2.x branch of `yajil` which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. This vulnerability was reported internally and has been assigned CVE-2022-24795. '
|
||||
- Support bundles could include sensitive files if {% data variables.product.prodname_actions %} was enabled.
|
||||
- Packages have been updated to the latest security versions.
|
||||
bugs:
|
||||
- The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release.
|
||||
- In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time.
|
||||
- A subset of internal configuration files are more reliably updated after a hotpatch.
|
||||
- The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly.
|
||||
- In a cluster environment, Git LFS operations could fail with failed internal API calls that crossed multiple web nodes.
|
||||
- Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges.
|
||||
- In some cluster topologies, webhook delivery information was not available.
|
||||
- In HA configurations, tearing down a replica would fail if {% data variables.product.prodname_actions %} had previously been enabled.
|
||||
- Elasticsearch health checks would not allow a yellow cluster status when running migrations.
|
||||
- Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account.
|
||||
- When using `ghe-migrator` or exporting from {% data variables.product.prodname_dotcom_the_website %}, a long-running export would fail when data was deleted mid-export.
|
||||
- Links to inaccessible pages were removed.
|
||||
- Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team.
|
||||
- A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail.
|
||||
- The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available.
|
||||
- The "Site admin mode" link in the site footer did not change state when clicked.
|
||||
changes:
|
||||
- Memcached connection limits were increased to better accommodate large cluster topologies.
|
||||
- More effectively identify and delete webhook logs that are outside of the webhook log retention window.
|
||||
- The Dependency Graph API previously ran with a statically defined port.
|
||||
- The default shard counts for cluster-related Elasticsearch shard settings have been updated.
|
||||
- The “Triage” and “Maintain” team roles are preserved during repository migrations.
|
||||
- '`NotProcessedError` exceptions were occurring unnecessarily.'
|
||||
- Performance has been improved for web requests made by enterprise owners.
|
||||
known_issues:
|
||||
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
|
||||
- On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
|
||||
- Custom firewall rules are removed during the upgrade process.
|
||||
- Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
|
||||
- Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
|
||||
- When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
|
||||
- If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`.
|
||||
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
|
||||
43
data/release-notes/enterprise-server/3-2/11.yml
Normal file
43
data/release-notes/enterprise-server/3-2/11.yml
Normal file
@@ -0,0 +1,43 @@
|
||||
date: '2022-04-04'
|
||||
sections:
|
||||
security_fixes:
|
||||
- 'MEDIUM: A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} Management Console that allowed the bypass of CSRF protections. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.5 and was fixed in versions 3.1.19, 3.2.11, 3.3.6, 3.4.1. This vulnerability was reported via the {% data variables.product.prodname_dotcom %} Bug Bounty program and has been assigned CVE-2022-23732.'
|
||||
- 'MEDIUM: An integer overflow vulnerability was identified in the 1.x branch and the 2.x branch of `yajil` which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. This vulnerability was reported internally and has been assigned CVE-2022-24795. '
|
||||
- Support bundles could include sensitive files if {% data variables.product.prodname_actions %} was enabled.
|
||||
- Packages have been updated to the latest security versions.
|
||||
bugs:
|
||||
- Minio processes would have high CPU usage if an old configuration option was present after upgrading {% data variables.product.prodname_ghe_server %}.
|
||||
- The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release.
|
||||
- In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time.
|
||||
- A subset of internal configuration files are more reliably updated after a hotpatch.
|
||||
- The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly.
|
||||
- In a cluster environment, Git LFS operations could fail with failed internal API calls that crossed multiple web nodes.
|
||||
- Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges.
|
||||
- In some cluster topologies, webhook delivery information was not available.
|
||||
- In HA configurations, tearing down a replica would fail if {% data variables.product.prodname_actions %} had previously been enabled.
|
||||
- Elasticsearch health checks would not allow a yellow cluster status when running migrations.
|
||||
- Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account.
|
||||
- When using `ghe-migrator` or exporting from {% data variables.product.prodname_dotcom_the_website %}, a long-running export would fail when data was deleted mid-export.
|
||||
- The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job.
|
||||
- Links to inaccessible pages were removed.
|
||||
- Navigating away from a comparison of two commits in the web UI would have the diff persist in other pages.
|
||||
- Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team.
|
||||
- The [Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user) API endpoint would respond with an error when attempting to remove a member managed externally by a SCIM group.
|
||||
- A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail.
|
||||
- The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available.
|
||||
- The "Site admin mode" link in the site footer did not change state when clicked.
|
||||
- 'The `spokesctl cache-policy rm` command no longer fails with the message `error: failed to delete cache policy`.'
|
||||
changes:
|
||||
- Memcached connection limits were increased to better accommodate large cluster topologies.
|
||||
- The Dependency Graph API previously ran with a statically defined port.
|
||||
- The default shard counts for cluster-related Elasticsearch shard settings have been updated.
|
||||
- The “Triage” and “Maintain” team roles are preserved during repository migrations.
|
||||
- Performance has been improved for web requests made by enterprise owners.
|
||||
known_issues:
|
||||
- On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
|
||||
- Custom firewall rules are removed during the upgrade process.
|
||||
- Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
|
||||
- Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
|
||||
- When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
|
||||
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
|
||||
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
|
||||
48
data/release-notes/enterprise-server/3-3/6.yml
Normal file
48
data/release-notes/enterprise-server/3-3/6.yml
Normal file
@@ -0,0 +1,48 @@
|
||||
date: '2022-04-04'
|
||||
sections:
|
||||
security_fixes:
|
||||
- 'MEDIUM: A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} Management Console that allowed the bypass of CSRF protections. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.5 and was fixed in versions 3.1.19, 3.2.11, 3.3.6, 3.4.1. This vulnerability was reported via the {% data variables.product.prodname_dotcom %} Bug Bounty program and has been assigned CVE-2022-23732.'
|
||||
- 'MEDIUM: An integer overflow vulnerability was identified in the 1.x branch and the 2.x branch of `yajil` which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. This vulnerability was reported internally and has been assigned CVE-2022-24795. '
|
||||
- Support bundles could include sensitive files if {% data variables.product.prodname_actions %} was enabled.
|
||||
- Packages have been updated to the latest security versions.
|
||||
bugs:
|
||||
- When enabling {% data variables.product.prodname_dependabot %}, an error caused some security advisories to temporarily read as no-longer applicable.
|
||||
- Minio processes would have high CPU usage if an old configuration option was present after upgrading {% data variables.product.prodname_ghe_server %}.
|
||||
- The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release.
|
||||
- In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time.
|
||||
- A subset of internal configuration files are more reliably updated after a hotpatch.
|
||||
- The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly.
|
||||
- In a cluster environment, Git LFS operations could fail with failed internal API calls that crossed multiple web nodes.
|
||||
- Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges.
|
||||
- In some cluster topologies, webhook delivery information was not available.
|
||||
- Elasticsearch health checks would not allow a yellow cluster status when running migrations.
|
||||
- Repositories would display a non-functional Discussions tab in the web UI.
|
||||
- Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account.
|
||||
- Links to inaccessible pages were removed.
|
||||
- The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job.
|
||||
- Some instances experienced high CPU usage due to large amounts unnecessary background jobs being queued.
|
||||
- LDAP user sync jobs would fail when trying to sync GPG keys that had been synced previously.
|
||||
- Following a link to a pull request from the users Pull Request dashboard would result in the repository header not loading.
|
||||
- Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team.
|
||||
- The remove team membership API endpoint would respond with an error when attempting to remove member externally managed via a SCIM Group.
|
||||
- A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail.
|
||||
- The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available.
|
||||
- The "Site admin mode" link in the site footer did not change state when clicked.
|
||||
- 'The `spokesctl cache-policy rm` command no longer fails with the message `error: failed to delete cache policy`.'
|
||||
changes:
|
||||
- Memcached connection limits were increased to better accommodate large cluster topologies.
|
||||
- The Dependency Graph API previously ran with a statically defined port.
|
||||
- The default shard counts for cluster-related Elasticsearch shard settings have been updated.
|
||||
- When filtering enterprise members by organization role on the "People" page, the text for the dropdown menu items has been improved.
|
||||
- The “Triage” and “Maintain” team roles are preserved during repository migrations.
|
||||
- Performance has been improved for web requests made by enterprise owners.
|
||||
known_issues:
|
||||
- After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command.
|
||||
- On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
|
||||
- Custom firewall rules are removed during the upgrade process.
|
||||
- Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
|
||||
- Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
|
||||
- When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
|
||||
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
|
||||
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
|
||||
- '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
|
||||
98
data/release-notes/enterprise-server/3-4/1.yml
Normal file
98
data/release-notes/enterprise-server/3-4/1.yml
Normal file
@@ -0,0 +1,98 @@
|
||||
date: '2022-04-04'
|
||||
sections:
|
||||
security_fixes:
|
||||
- 'MEDIUM: A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} Management Console that allowed the bypass of CSRF protections. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.5 and was fixed in versions 3.1.19, 3.2.11, 3.3.6, 3.4.1. This vulnerability was reported via the {% data variables.product.prodname_dotcom %} Bug Bounty program and has been assigned CVE-2022-23732.'
|
||||
- 'MEDIUM: An integer overflow vulnerability was identified in the 1.x branch and the 2.x branch of `yajil` which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. This vulnerability was reported internally and has been assigned CVE-2022-24795. '
|
||||
- Support bundles could include sensitive files if {% data variables.product.prodname_actions %} was enabled.
|
||||
- Packages have been updated to the latest security versions.
|
||||
bugs:
|
||||
- A workflow run may not complete if it uses composite-actions.
|
||||
- When enabling {% data variables.product.prodname_dependabot %}, an error caused some security advisories to temporarily read as no-longer applicable.
|
||||
- Minio processes would have high CPU usage if an old configuration option was present after upgrading {% data variables.product.prodname_ghe_server %}.
|
||||
- The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release.
|
||||
- In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time.
|
||||
- A subset of internal configuration files are more reliably updated after a hotpatch.
|
||||
- The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly.
|
||||
- Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges.
|
||||
- In some cluster topologies, webhook delivery information was not available.
|
||||
- The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job.
|
||||
- Elasticsearch health checks would not allow a yellow cluster status when running migrations.
|
||||
- When using the [Migrations API](/rest/reference/migrations), queued export jobs were not processed.
|
||||
- Repositories would display a non-functional Discussions tab in the web UI.
|
||||
- Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account.
|
||||
- LDAP user sync jobs would fail when trying to sync GPG keys that had been synced previously.
|
||||
- Links to inaccessible pages were removed.
|
||||
- Some instances experienced high CPU usage due to large amounts unnecessary background jobs being queued.
|
||||
- Empty repositories didnt sync correctly to cache servers.
|
||||
- Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team.
|
||||
- The remove team membership API endpoint would respond with an error when attempting to remove member externally managed via a SCIM Group.
|
||||
- A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail.
|
||||
- The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available.
|
||||
- The "Site admin mode" link in the site footer did not change state when clicked.
|
||||
changes:
|
||||
- Memcached connection limits were increased to better accommodate large cluster topologies.
|
||||
- The Dependency Graph API previously ran with a statically defined port.
|
||||
- The default shard counts for cluster-related Elasticsearch shard settings have been updated.
|
||||
- The [Migrations API](/rest/reference/migrations) now generates exports of repositories.
|
||||
- When filtering enterprise members by organization role on the "People" page, the text for the dropdown menu items has been improved.
|
||||
- The “Triage” and “Maintain” team roles are preserved during repository migrations.
|
||||
- Using ghe-migrator or exporting from GitHub.com, an export would not include Pull Request attachments.
|
||||
- Performance has been improved for web requests made by enterprise owners.
|
||||
known_issues:
|
||||
- On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
|
||||
- Custom firewall rules are removed during the upgrade process.
|
||||
- Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
|
||||
- Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
|
||||
- When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
|
||||
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
|
||||
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
|
||||
- Actions services need to be restarted after restoring appliance from backup taken on a different host.
|
||||
|
||||
deprecations:
|
||||
- heading: Deprecation of GitHub Enterprise Server 3.0
|
||||
notes:
|
||||
- '**{% data variables.product.prodname_ghe_server %} 3.0 was discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
|
||||
- heading: Deprecation of GitHub Enterprise Server 3.1
|
||||
notes:
|
||||
- '**{% data variables.product.prodname_ghe_server %} 3.1 will be discontinued on June 3, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
|
||||
|
||||
- heading: Deprecation of XenServer Hypervisor support
|
||||
notes:
|
||||
# https://github.com/github/docs-content/issues/4439
|
||||
- Starting in {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer was deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns.
|
||||
|
||||
- heading: Deprecation of the Content Attachments API preview
|
||||
notes:
|
||||
#
|
||||
- Due to low usage, we have deprecated the Content References API preview in {% data variables.product.prodname_ghe_server %} 3.4. The API was previously accessible with the `corsair-preview` header. Users can continue to navigate to external URLs without this API. Any registered usages of the Content References API will no longer receive a webhook notification for URLs from your registered domain(s) and we no longer return valid response codes for attempted updates to existing content attachments.
|
||||
|
||||
- heading: Deprecation of the Codes of Conduct API preview
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/1708
|
||||
- 'The Codes of Conduct API preview, which was accessible with the `scarlet-witch-preview` header, is deprecated and no longer accessible in {% data variables.product.prodname_ghe_server %} 3.4. We instead recommend using the "[Get community profile metrics](/rest/reference/repos#get-community-profile-metrics)" endpoint to retrieve information about a repository''s code of conduct. For more information, see the "[Deprecation Notice: Codes of Conduct API preview](https://github.blog/changelog/2021-10-06-deprecation-notice-codes-of-conduct-api-preview/)" in the {% data variables.product.prodname_dotcom %} changelog.'
|
||||
|
||||
- heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/1316
|
||||
- |
|
||||
Starting with {% data variables.product.prodname_ghe_server %} 3.4, the [deprecated version of the OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#endpoints-affected) have been removed. If you encounter 404 error messages on these endpoints, convert your code to the versions of the OAuth Application API that do not have `access_tokens` in the URL. We've also disabled the use of API authentication using query parameters. We instead recommend using [API authentication in the request header](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make).
|
||||
|
||||
- heading: Deprecation of the CodeQL runner
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/1632
|
||||
- The {% data variables.product.prodname_codeql %} runner is deprecated in {% data variables.product.prodname_ghe_server %} 3.4 and is no longer supported. The deprecation only affects users who use {% data variables.product.prodname_codeql %} code scanning in third party CI/CD systems; {% data variables.product.prodname_actions %} users are not affected. We strongly recommend that customers migrate to the {% data variables.product.prodname_codeql %} CLI, which is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/).
|
||||
|
||||
- heading: Deprecation of custom bit-cache extensions
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/1415
|
||||
- |
|
||||
Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards.
|
||||
|
||||
Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated.
|
||||
|
||||
Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed.
|
||||
|
||||
To start a repository maintenance task manually, browse to `https://<hostname>/stafftools/repositories/<owner>/<repository>/network` for each affected repository and click the Schedule button.
|
||||
|
||||
backups:
|
||||
- '{% data variables.product.prodname_ghe_server %} 3.4 requires at least [GitHub Enterprise Backup Utilities 3.4.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).'
|
||||
1
data/reusables/codespaces/restrict-port-visibility.md
Normal file
1
data/reusables/codespaces/restrict-port-visibility.md
Normal file
@@ -0,0 +1 @@
|
||||
Organization owners can restrict the ability to make forward ports available publicly or within the organization. For more information, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)."
|
||||
@@ -4,7 +4,7 @@ The following table shows, for each package manager:
|
||||
- Whether dependencies in private {% data variables.product.prodname_dotcom %} repositories or registries are supported
|
||||
- Whether vendored dependencies are supported
|
||||
|
||||
Package manager | YAML value | Supported versions | Private repositories | Private registries | Vendoring
|
||||
Package manager | YAML value | Supported versions | Private repositories | Private registries | Vendoring
|
||||
---------------|------------------|------------------|:---:|:---:|:---:
|
||||
Bundler | `bundler` | v1, v2 | | **✓** | **✓** |
|
||||
Cargo | `cargo` | v1 | **✓** | **✓** | |
|
||||
@@ -22,14 +22,25 @@ NuGet | `nuget` | <= 4.8<sup>[3]</sup> | **✓** | **✓** | |
|
||||
pip | `pip` | v21.1.2 | | **✓** | |
|
||||
pipenv | `pip` | <= 2021-05-29 | | **✓** | |
|
||||
pip-compile | `pip` | 6.1.0 | | **✓** | |
|
||||
poetry | `pip` | v1 | | **✓** | |
|
||||
poetry | `pip` | v1 | | **✓** | |{% ifversion fpt or ghec or ghes > 3.4 %}
|
||||
pub | `pub` | v2 <sup>[4]</sup> | | | |{% endif %}
|
||||
Terraform | `terraform` | >= 0.13, <= 1.0 | **✓** | **✓** | |
|
||||
yarn | `npm` | v1 | **✓** | **✓** | |
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** For package managers such as `pipenv` and `poetry`, you need to use the `pip` YAML value. For example, if you use `poetry` to manage your Python dependencies and want {% data variables.product.prodname_dependabot %} to monitor your dependency manifest file for new versions, use `package-ecosystem: "pip"` in your *dependabot.yml* file.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
[1] {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle`, `build.gradle.kts` (for Kotlin projects), and files included via the `apply` declaration that have `dependencies` in the filename. Note that `apply` does not support `apply to`, recursion, or advanced syntaxes (for example, Kotlin's `apply` with `mapOf`, filenames defined by property).
|
||||
|
||||
[2] {% data variables.product.prodname_dependabot %} doesn't run Maven but supports updates to `pom.xml` files.
|
||||
|
||||
[3] {% data variables.product.prodname_dependabot %} doesn't run the NuGet CLI but does support most features up until version 4.8.
|
||||
|
||||
For package managers such as `pipenv` and `poetry`, you need to use the `pip` YAML value. For example, if you use `poetry` to manage your Python dependencies and want {% data variables.product.prodname_dependabot %} to monitor your dependency manifest file for new versions, use `package-ecosystem: "pip"` in your *dependabot.yml* file.
|
||||
{% ifversion fpt or ghec or ghes > 3.4 %}[4] `pub` support is currently in beta. Any known limitations are subject to change. Note that {% data variables.product.prodname_dependabot %}:
|
||||
- Doesn't support updating git dependencies for `pub`.
|
||||
- Won't perform an update when the version that it tries to update to is ignored, even if an earlier version is available.
|
||||
|
||||
For information about configuring your _dependabot.yml_ file for `pub`, see "[Enabling support for beta-level ecosystems](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#enable-beta-ecosystems)." {% endif %}
|
||||
|
||||
@@ -1 +1,5 @@
|
||||
1. Click **Get the latest release of {% data variables.product.prodname_ghe_server %}**.
|
||||
1. Navigate to the image you want to use for your new instance.
|
||||
|
||||
- Navigate to [Release notes](/admin/release-notes).
|
||||
- In the right sidebar, click the version you want to download.
|
||||
- Click **Download {% data variables.product.prodname_ghe_server %} X.X.X**.
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. To download your license file, click **Download license**.
|
||||
1. Download your license. For more information, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)."
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
1. Navigate to [the {% data variables.product.prodname_ghe_server %} download page](https://enterprise.github.com/download).
|
||||
@@ -1 +1 @@
|
||||
1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Blocked users**.
|
||||
1. In the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Blocked users**.
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**
|
||||
@@ -1,7 +1,7 @@
|
||||
Before you can authorize a personal access token or SSH key, you must have a linked SAML identity. If you're a member of an organization where SAML SSO is enabled, you can create a linked identity by authenticating to your organization with your IdP at least once. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)."
|
||||
|
||||
After you authorize a personal access token or SSH key. The token or key will stay authorized until revoked in one of these ways.
|
||||
- An organization owner revokes the authorization.
|
||||
- An organization or enterprise owner revokes the authorization.
|
||||
- You are removed from the organization.
|
||||
- The scopes in a personal access token are edited, or the token is regenerated.
|
||||
- The personal access token expired as defined during creation.
|
||||
|
||||
5
data/reusables/saml/must-authorize-linked-identity.md
Normal file
5
data/reusables/saml/must-authorize-linked-identity.md
Normal file
@@ -0,0 +1,5 @@
|
||||
{% note %}
|
||||
|
||||
**Note:** If you have a linked identity for an organization, you can only use authorized personal access tokens and SSH keys with that organization, even if SAML is not enforced. You have a linked identity for an organization if you've ever authenticated via SAML SSO for that organization, unless an organization or enterprise owner later revoked the linked identity. For more information about revoking linked identities, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" and "[Viewing and managing a user's SAML access to your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)."
|
||||
|
||||
{% endnote %}
|
||||
@@ -16,8 +16,6 @@ services:
|
||||
HEROKU_APP_NAME: ${HEROKU_APP_NAME}
|
||||
ENABLED_LANGUAGES: ${ENABLED_LANGUAGES}
|
||||
DEPLOYMENT_ENV: ${DEPLOYMENT_ENV}
|
||||
RATE_LIMIT_MAX: ${RATE_LIMIT_MAX}
|
||||
SLOW_DOWN_MAX: ${SLOW_DOWN_MAX}
|
||||
HEROKU_PRODUCTION_APP: true
|
||||
PORT: 4000
|
||||
DD_AGENT_HOST: datadog-agent
|
||||
|
||||
@@ -1,4 +1,20 @@
|
||||
[
|
||||
{
|
||||
"schemaChanges": [
|
||||
{
|
||||
"title": "The GraphQL schema includes these changes:",
|
||||
"changes": [
|
||||
"Field `blocksCreations` was added to object type `BranchProtectionRule`",
|
||||
"Input field `blocksCreations` was added to input object type `CreateBranchProtectionRuleInput`",
|
||||
"Field `blocksCreations` was added to object type `RefUpdateRule`",
|
||||
"Input field `blocksCreations` was added to input object type `UpdateBranchProtectionRuleInput`"
|
||||
]
|
||||
}
|
||||
],
|
||||
"previewChanges": [],
|
||||
"upcomingChanges": [],
|
||||
"date": "2022-04-03"
|
||||
},
|
||||
{
|
||||
"schemaChanges": [
|
||||
{
|
||||
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@@ -8665,6 +8665,14 @@
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "blocksCreations",
|
||||
"description": "<p>Is branch creation a protected operation.</p>",
|
||||
"type": "Boolean!",
|
||||
"id": "boolean",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "branchProtectionRuleConflicts",
|
||||
"description": "<p>A list of conflicts matching branches protection rule and other branch protection rules.</p>",
|
||||
@@ -45300,6 +45308,14 @@
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "blocksCreations",
|
||||
"description": "<p>Can matching branches be created.</p>",
|
||||
"type": "Boolean!",
|
||||
"id": "boolean",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "pattern",
|
||||
"description": "<p>Identifies the protection rule pattern.</p>",
|
||||
@@ -75955,6 +75971,14 @@
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "blocksCreations",
|
||||
"description": "<p>Is branch creation a protected operation.</p>",
|
||||
"type": "Boolean",
|
||||
"id": "boolean",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "bypassForcePushActorIds",
|
||||
"description": "<p>A list of User or Team IDs allowed to bypass force push targeting matching branches.</p>",
|
||||
@@ -81633,6 +81657,14 @@
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "blocksCreations",
|
||||
"description": "<p>Is branch creation a protected operation.</p>",
|
||||
"type": "Boolean",
|
||||
"id": "boolean",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "branchProtectionRuleId",
|
||||
"description": "<p>The global relay id of the branch protection rule to be updated.</p>",
|
||||
|
||||
@@ -7388,6 +7388,14 @@
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "blocksCreations",
|
||||
"description": "<p>Is branch creation a protected operation.</p>",
|
||||
"type": "Boolean!",
|
||||
"id": "boolean",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "branchProtectionRuleConflicts",
|
||||
"description": "<p>A list of conflicts matching branches protection rule and other branch protection rules.</p>",
|
||||
@@ -39458,6 +39466,14 @@
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "blocksCreations",
|
||||
"description": "<p>Can matching branches be created.</p>",
|
||||
"type": "Boolean!",
|
||||
"id": "boolean",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "pattern",
|
||||
"description": "<p>Identifies the protection rule pattern.</p>",
|
||||
@@ -66045,6 +66061,14 @@
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "blocksCreations",
|
||||
"description": "<p>Is branch creation a protected operation.</p>",
|
||||
"type": "Boolean",
|
||||
"id": "boolean",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "bypassForcePushActorIds",
|
||||
"description": "<p>A list of User or Team IDs allowed to bypass force push targeting matching branches.</p>",
|
||||
@@ -70681,6 +70705,14 @@
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "blocksCreations",
|
||||
"description": "<p>Is branch creation a protected operation.</p>",
|
||||
"type": "Boolean",
|
||||
"id": "boolean",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "branchProtectionRuleId",
|
||||
"description": "<p>The global relay id of the branch protection rule to be updated.</p>",
|
||||
|
||||
@@ -8665,6 +8665,14 @@
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "blocksCreations",
|
||||
"description": "<p>Is branch creation a protected operation.</p>",
|
||||
"type": "Boolean!",
|
||||
"id": "boolean",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "branchProtectionRuleConflicts",
|
||||
"description": "<p>A list of conflicts matching branches protection rule and other branch protection rules.</p>",
|
||||
@@ -45300,6 +45308,14 @@
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "blocksCreations",
|
||||
"description": "<p>Can matching branches be created.</p>",
|
||||
"type": "Boolean!",
|
||||
"id": "boolean",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "pattern",
|
||||
"description": "<p>Identifies the protection rule pattern.</p>",
|
||||
@@ -75955,6 +75971,14 @@
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "blocksCreations",
|
||||
"description": "<p>Is branch creation a protected operation.</p>",
|
||||
"type": "Boolean",
|
||||
"id": "boolean",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "bypassForcePushActorIds",
|
||||
"description": "<p>A list of User or Team IDs allowed to bypass force push targeting matching branches.</p>",
|
||||
@@ -81633,6 +81657,14 @@
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "blocksCreations",
|
||||
"description": "<p>Is branch creation a protected operation.</p>",
|
||||
"type": "Boolean",
|
||||
"id": "boolean",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "branchProtectionRuleId",
|
||||
"description": "<p>The global relay id of the branch protection rule to be updated.</p>",
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:7517e01fbcf6a34911dddff4ed4f9b9ac2f7f3ed16782d145ba7c1e084424894
|
||||
size 659778
|
||||
oid sha256:2438291cfe769fe6cc51a4f4a45a5ca870eeb61241526066ca2bc1c4235f521b
|
||||
size 659615
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ff40ff6e17b39ccf8dfddfcc425071ff8789d8de83cad72506f2ec70c284a483
|
||||
size 1321501
|
||||
oid sha256:c06e3fc045e7e3c35eecf4b839edfe63c9de8b01337dfa3435a83a2510e687a2
|
||||
size 1319234
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:6dcc84364ab5a093373874d00ba2a60a1c5e53fc5ca6671c7d92bc7ed566cf02
|
||||
size 882778
|
||||
oid sha256:08829b3b159c5ccc20cb6d640af93a88968525b357a98b65a2634964abee3355
|
||||
size 881451
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b5efa5d49b5eb1ab0dc3768525149bd012f233bf1cc809c067ccc67280546b47
|
||||
size 3389468
|
||||
oid sha256:24dc037aa5e7bee85003710c78a19fb79dbf900a3fd67b94345147ab2fc04fc5
|
||||
size 3388118
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:19fe499e796aedb3c9c5ea4fe3dbfc6be147ea8d5fac7b8100dc5d412dc1317c
|
||||
size 608326
|
||||
oid sha256:36d177db26a6a78f9fca8a4c9e3551becc50031fe3a31ba65c827e8a48b1270e
|
||||
size 608295
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4eda813a2dd6cc9a888f79525d618225742a4d4e68d8c28cac1bde6441a7914e
|
||||
size 2543009
|
||||
oid sha256:61ca2115beaa8ba94aa91dc2ca339360b2e0b40d6401d5b4eab5fd6f243270b9
|
||||
size 2543136
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:fde9c262aa84c1cb3cfd9a193768fcd0074cbb080c64b160bf5853af136515bb
|
||||
size 672830
|
||||
oid sha256:f11c0ea29c90e757beae913af5168e7ea69adf5ee746570a61cee2a1c08683f4
|
||||
size 672959
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b0931f122359ad6567f577a6c8aa8ecca253390c5eb846b71bd8d199174720f9
|
||||
size 3570853
|
||||
oid sha256:4e751743842f58888bfff6c32f240b5a4829e4e154f79c2182441567de1e9fc3
|
||||
size 3574301
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:6ae167f26778b6f656f795c33796b8c8cdc734431452e73cb5c6c43f16ae9b13
|
||||
size 598623
|
||||
oid sha256:430d5629ab21023026e4bb65ff981361ab3e7bc1b83f7938b08dd050164d3da1
|
||||
size 599107
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e1c43595c302fbb81dbbd5120c28ad4fa4cee720e6c0e82341e929dad94d229d
|
||||
size 2447939
|
||||
oid sha256:1f0ccce1a6c8a826ad595c0bd77b52a075ca5840abd0e4c0865041c15a3e3448
|
||||
size 2449876
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:40b29b3ae2aa2b6658a82fa8ad4d4b5b6697965d42468b7d08e89e8f4ec6c5fb
|
||||
size 677047
|
||||
oid sha256:595385b9d3637384fcd3820f7fa8ebe93de73160cd808bcd6425c94f2749ef14
|
||||
size 676955
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:038823a05ca0664f80f40991fe2872057658c95ad699922ed03f5d777fd7bcfd
|
||||
size 1350842
|
||||
oid sha256:d38584d5303ac01c18ff6dcded9e591a296bd809a9f09bb0f886e652e39157a9
|
||||
size 1350152
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:3edb7c1ec7ddee32fd456cadaa7c48006df5c78297b23f8478d188014346f548
|
||||
size 910825
|
||||
oid sha256:5ce9e8821db866d36a5afbc8c1d24e8d039b334800497328a6c32e47fba660ce
|
||||
size 911583
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:256808b990c60414f88b2e1f66062452f7fa983d4aa043a505a218004078e2ad
|
||||
size 3506087
|
||||
oid sha256:a8c6776c2d63898fee63d9199ccedf44fecd512b4f2435b62bf21b5fda218940
|
||||
size 3504978
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e1755df9c5ea7865b2e78ae077775824ec110812e9e59ce9ccadcad5186fe723
|
||||
size 624302
|
||||
oid sha256:80ceb12758bf516b73148d31752e1129d31fbb495f3ddb6017aa87239794b51a
|
||||
size 624348
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8431e443dde93bcde4caa9c98ca8daf361bc388fec8b951250a726661d78719a
|
||||
size 2612696
|
||||
oid sha256:0b4e805971f73124c3e61654d8b3dc9aa5ff5940eaf95d860fdbf36c53acbe3b
|
||||
size 2613672
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:520b6b06a3cdab158dd80ae236aa9f27afac25832612771e5956d4f69c0ca6dc
|
||||
size 689254
|
||||
oid sha256:fc6901b2e1362e5fb5712430d58e1ded33d0d5dddd6739b99f8f7fb7e18f5e9f
|
||||
size 689366
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b44415fd29d97f3bd62478f2b6b6d8a14995d014dd79e4df38fb127413fcc24f
|
||||
size 3661884
|
||||
oid sha256:58460054e8b100f8db9836c9b64379696c943d0520089d82c602f9516938516f
|
||||
size 3662216
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:60702a6c3e1ccb6c0d9c4deb3845ea1e66900ab9acf65a21abab8ada1f05ca52
|
||||
size 615013
|
||||
oid sha256:3d9820eccd3a32fe9e8d096114c52bff2904832335224445f1c6c625657c1aba
|
||||
size 615462
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:51ea7b3d8fd915b6c4d7a5ac5505111b0c7dc18070d1000d1c3cb51ec034f52e
|
||||
size 2506589
|
||||
oid sha256:75474af569db90ee9cefd19ffcf6a82ddc41116afd348aec7c21d059ee83e328
|
||||
size 2508905
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:81547adec86ba5d58479ac8e383096f9e0f2439536e9e531011f009da19746a3
|
||||
size 700176
|
||||
oid sha256:3d6eb7a3311168c836ae0c7cb28744affa87fe92e34dd5a0c7656679bf80b687
|
||||
size 699814
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8306621031f95df32cb6349c2830f02ff0d8ae291170d22bdd58fbab5c083876
|
||||
size 1399069
|
||||
oid sha256:72534deda0acbf787a48d90741be76d991b3f373ceb0320b8ec6b76e352035a9
|
||||
size 1397239
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e42843b7daadc444bb6f6ee9727447dcbeec5651c7d726861ae83734f48c5113
|
||||
size 945174
|
||||
oid sha256:29ffcc21336d64034d82642f5fcc1c7fff62f874db1c3fa36c723423fd724f36
|
||||
size 945473
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8db0adeb8a71a85c26d725f9513f453831c12f4b3f2d6e68c70a40c4e99ae3f5
|
||||
size 3620812
|
||||
oid sha256:dddf4a5ef06a6d938970aec09d2bd045b7c8e0673894dd020122145be69a67a8
|
||||
size 3623151
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b7c0da2ca3865595bb29bfc1a655787b2a9a7c33f32b521d773481917bebda96
|
||||
size 643241
|
||||
oid sha256:3c2f07890bdf73f23c924be1537e87892af224d2aa82ff9dc05ee51afe6e6c3f
|
||||
size 643931
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:96aac128753cd3ab25452efaad12e2bc0e6937b40dc7d1adfb30076b51e6b3f9
|
||||
size 2698106
|
||||
oid sha256:cf7f01ceb30e1110ee028e2d696fa99f74aa5681567a34ada73b1825bc6f3b2e
|
||||
size 2699981
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:da87efa163e99603acaa0f568fcc0711203b7a4b823d4fd79e1517a9e5e598e3
|
||||
size 713526
|
||||
oid sha256:237b28641f4f45991f6d83c22814853e04784bac4898895234ad361032e0ce33
|
||||
size 713289
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:3b1db22036da15df4d3689deff80b5a16e039a42c89df5cefdadde5dece0a80e
|
||||
size 3784806
|
||||
oid sha256:0776d77e6cba356fe9f1539b2518b33ef64312fa91f4f747ceb7cafcd7d99d36
|
||||
size 3785864
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:5e71ff44e4983d43653193c34d4c4865ca1473029d891ebb1aa9d4de633d7099
|
||||
size 634290
|
||||
oid sha256:119a8b38f932ea26c0c7d3da05b7cca4030b6b6155942f77141c38a681ce3685
|
||||
size 634842
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:1ae584923688023509a5dfe9c285fcd8cf0c0c3b24ae3026004686edd048fe03
|
||||
size 2589067
|
||||
oid sha256:53073d52d3a91db3db4f93e4f3520626010146fb7cbe511c2a9aac7a248d2ce0
|
||||
size 2589936
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b280898cdc44b4c3f8ad0bd66f87544455c8b378522caf0f59971f9662734b12
|
||||
size 703466
|
||||
oid sha256:c6a4634bac4349003da9435d8cb4c8468a53b2b5ea766d39c5a63fb7afb0960b
|
||||
size 702579
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:16a11a94d376e229dfe38944e5a1d895e7386d97dc061c51565be9806679d3f4
|
||||
size 1408256
|
||||
oid sha256:eb191e964b896fb3c0019268752be4fa8b9b7b0265396fe25a4a91efd5b6aba1
|
||||
size 1406082
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:a860c4c4be7ecc3d8a94504fcf057cede503e66a546464810e63c4ba306a869c
|
||||
size 955723
|
||||
oid sha256:b471553b39f8b349947cb177b349df22a3e2db651af9a76aee451356e30dc722
|
||||
size 955744
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user