Merge branch 'main' into main
This commit is contained in:
mc
6
.github/allowed-actions.js
vendored
6
.github/allowed-actions.js
vendored
@@ -7,7 +7,7 @@ export default [
|
||||
'actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f', // v2.3.4
|
||||
'actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d', // v4.0.2
|
||||
'actions/labeler@5f867a63be70efff62b767459b009290364495eb', // v2.2.0
|
||||
'actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f', // v2.2.0
|
||||
'actions/setup-node@270253e841af726300e85d718a5f606959b2903c', // v2.4.1
|
||||
'actions/stale@cdf15f641adb27a71842045a94023bef6945e3aa', // v4.0.0
|
||||
'actions/upload-artifact@27121b0bdffd731efa15d66772be8dc71245d074', // v2.2.4
|
||||
'alex-page/github-project-automation-plus@bb266ff4dde9242060e2d5418e120a133586d488', // v0.8.1
|
||||
@@ -29,12 +29,12 @@ export default [
|
||||
'peter-evans/create-issue-from-file@b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e',
|
||||
'peter-evans/create-or-update-comment@5221bf4aa615e5c6e95bb142f9673a9c791be2cd',
|
||||
'peter-evans/create-pull-request@7380612b49221684fefa025244f2ef4008ae50ad', // v3.10.1
|
||||
'peter-evans/find-comment@0da1f4fc1f20cd898368bd56089d391df418f52f',
|
||||
'peter-evans/find-comment@d2dae40ed151c634e4189471272b57e76ec19ba8', // v1.3.0
|
||||
'rachmari/actions-add-new-issue-to-column@1a459ef92308ba7c9c9dc2fcdd72f232495574a9',
|
||||
'repo-sync/github-sync@3832fe8e2be32372e1b3970bbae8e7079edeec88',
|
||||
'repo-sync/pull-request@65194d8015be7624d231796ddee1cd52a5023cb3', // v2.6
|
||||
'someimportantcompany/github-actions-slack-message@0b470c14b39da4260ed9e3f9a4f1298a74ccdefd',
|
||||
'tjenkinson/gh-action-auto-merge-dependency-updates@4d7756c04d9d999c5968697a621b81c47f533d61',
|
||||
'tjenkinson/gh-action-auto-merge-dependency-updates@c47f6255e06f36e84201ee940466e731ffa6e885', // v1.1.1
|
||||
'Bhacaz/checkout-files@c8f01756bfd894ba746d5bf48205e19000b0742b', // v1.0.0
|
||||
'EndBug/add-and-commit@2bdc0a61a03738a1d1bda24d566ad0dbe3083d87',
|
||||
]
|
||||
|
||||
2
.github/workflows/60-days-stale-check.yml
vendored
2
.github/workflows/60-days-stale-check.yml
vendored
@@ -24,4 +24,4 @@ jobs:
|
||||
stale-issue-label: 'stale'
|
||||
stale-pr-label: 'stale'
|
||||
exempt-pr-labels: 'never-stale'
|
||||
exempt-issue-labels: 'never-stale'
|
||||
exempt-issue-labels: 'never-stale, help wanted, waiting for review'
|
||||
|
||||
2
.github/workflows/automerge-dependencies.yml
vendored
2
.github/workflows/automerge-dependencies.yml
vendored
@@ -36,7 +36,7 @@ jobs:
|
||||
}}
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: tjenkinson/gh-action-auto-merge-dependency-updates@4d7756c04d9d999c5968697a621b81c47f533d61
|
||||
- uses: tjenkinson/gh-action-auto-merge-dependency-updates@c47f6255e06f36e84201ee940466e731ffa6e885
|
||||
with:
|
||||
repo-token: ${{ secrets.GITHUB_TOKEN }}
|
||||
allowed-actors: dependabot[bot]
|
||||
|
||||
2
.github/workflows/browser-test.yml
vendored
2
.github/workflows/browser-test.yml
vendored
@@ -25,7 +25,7 @@ jobs:
|
||||
run: git lfs checkout
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
@@ -24,7 +24,7 @@ jobs:
|
||||
- name: Check out repo's default branch
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
@@ -39,7 +39,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
@@ -41,7 +41,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
@@ -102,7 +102,7 @@ jobs:
|
||||
core.setOutput('changesTable', markdownTable)
|
||||
|
||||
- name: Find content directory changes comment
|
||||
uses: peter-evans/find-comment@0da1f4fc1f20cd898368bd56089d391df418f52f
|
||||
uses: peter-evans/find-comment@d2dae40ed151c634e4189471272b57e76ec19ba8
|
||||
id: findComment
|
||||
with:
|
||||
issue-number: ${{ github.event.pull_request.number }}
|
||||
|
||||
2
.github/workflows/crowdin-cleanup.yml
vendored
2
.github/workflows/crowdin-cleanup.yml
vendored
@@ -21,7 +21,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/docs-review-collect.yml
vendored
2
.github/workflows/docs-review-collect.yml
vendored
@@ -23,7 +23,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/enterprise-dates.yml
vendored
2
.github/workflows/enterprise-dates.yml
vendored
@@ -35,7 +35,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
@@ -42,7 +42,7 @@ jobs:
|
||||
token: ${{ secrets.DOCUBOT_REPO_PAT }}
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
4
.github/workflows/js-lint.yml
vendored
4
.github/workflows/js-lint.yml
vendored
@@ -19,7 +19,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
@@ -28,4 +28,4 @@ jobs:
|
||||
run: npm ci
|
||||
|
||||
- name: Run linter
|
||||
run: npx eslint .
|
||||
run: npm run lint
|
||||
|
||||
2
.github/workflows/link-check-dotcom.yml
vendored
2
.github/workflows/link-check-dotcom.yml
vendored
@@ -21,7 +21,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/link-check-ghae.yml
vendored
2
.github/workflows/link-check-ghae.yml
vendored
@@ -21,7 +21,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/link-check-ghes.yml
vendored
2
.github/workflows/link-check-ghes.yml
vendored
@@ -21,7 +21,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/open-enterprise-issue.yml
vendored
2
.github/workflows/open-enterprise-issue.yml
vendored
@@ -19,7 +19,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/openapi-decorate.yml
vendored
2
.github/workflows/openapi-decorate.yml
vendored
@@ -29,7 +29,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/openapi-schema-check.yml
vendored
2
.github/workflows/openapi-schema-check.yml
vendored
@@ -32,7 +32,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/os-ready-for-review.yml
vendored
2
.github/workflows/os-ready-for-review.yml
vendored
@@ -47,7 +47,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/pa11y.yml
vendored
2
.github/workflows/pa11y.yml
vendored
@@ -17,7 +17,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/ping-staging-apps.yml
vendored
2
.github/workflows/ping-staging-apps.yml
vendored
@@ -18,7 +18,7 @@ jobs:
|
||||
steps:
|
||||
- uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
- name: Setup node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/prod-build-deploy.yml
vendored
2
.github/workflows/prod-build-deploy.yml
vendored
@@ -34,7 +34,7 @@ jobs:
|
||||
run: git lfs checkout
|
||||
|
||||
- name: Setup node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/ready-for-doc-review.yml
vendored
2
.github/workflows/ready-for-doc-review.yml
vendored
@@ -18,7 +18,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
@@ -27,7 +27,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
@@ -49,7 +49,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/remove-unused-assets.yml
vendored
2
.github/workflows/remove-unused-assets.yml
vendored
@@ -24,7 +24,7 @@ jobs:
|
||||
- name: Checkout
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
4
.github/workflows/repo-sync.yml
vendored
4
.github/workflows/repo-sync.yml
vendored
@@ -98,7 +98,7 @@ jobs:
|
||||
|
||||
# Set up npm and run npm ci to run husky to get githooks for LFS
|
||||
- name: Setup node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
@@ -143,7 +143,7 @@ jobs:
|
||||
if: ${{ steps.find-pull-request.outputs.number }}
|
||||
uses: juliangruber/approve-pull-request-action@c530832d4d346c597332e20e03605aa94fa150a8
|
||||
with:
|
||||
github-token: ${{ secrets.DOCUBOT_REPO_PAT }}
|
||||
github-token: ${{ secrets.GITHUB_TOKEN }}
|
||||
number: ${{ steps.find-pull-request.outputs.number }}
|
||||
|
||||
# Because we get far too much spam ;_;
|
||||
|
||||
2
.github/workflows/staging-build-pr.yml
vendored
2
.github/workflows/staging-build-pr.yml
vendored
@@ -72,7 +72,7 @@ jobs:
|
||||
run: exit 1
|
||||
|
||||
- name: Setup node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
4
.github/workflows/staging-deploy-pr.yml
vendored
4
.github/workflows/staging-deploy-pr.yml
vendored
@@ -293,7 +293,7 @@ jobs:
|
||||
|
||||
- if: ${{ github.repository == 'github/docs-internal' }}
|
||||
name: Setup node to clone early access
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
@@ -457,7 +457,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/staging-undeploy-pr.yml
vendored
2
.github/workflows/staging-undeploy-pr.yml
vendored
@@ -61,7 +61,7 @@ jobs:
|
||||
persist-credentials: 'false'
|
||||
|
||||
- name: Setup node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/sync-search-indices.yml
vendored
2
.github/workflows/sync-search-indices.yml
vendored
@@ -53,7 +53,7 @@ jobs:
|
||||
token: ${{ secrets.DOCS_BOT_FR }}
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
6
.github/workflows/test-windows.yml
vendored
6
.github/workflows/test-windows.yml
vendored
@@ -32,7 +32,7 @@ jobs:
|
||||
persist-credentials: 'false'
|
||||
|
||||
- name: Setup node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
@@ -52,6 +52,4 @@ jobs:
|
||||
run: npm run build
|
||||
|
||||
- name: Run tests
|
||||
run: npx jest tests/${{ matrix.test-group }}/
|
||||
env:
|
||||
NODE_OPTIONS: '--max_old_space_size=8192'
|
||||
run: npm run test tests/${{ matrix.test-group }}/
|
||||
|
||||
6
.github/workflows/test.yml
vendored
6
.github/workflows/test.yml
vendored
@@ -37,7 +37,7 @@ jobs:
|
||||
persist-credentials: 'false'
|
||||
|
||||
- name: Setup node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
@@ -57,6 +57,4 @@ jobs:
|
||||
run: npm run build
|
||||
|
||||
- name: Run tests
|
||||
run: npx jest tests/${{ matrix.test-group }}/
|
||||
env:
|
||||
NODE_OPTIONS: '--max_old_space_size=8192 --experimental-vm-modules'
|
||||
run: npm run test tests/${{ matrix.test-group }}/
|
||||
|
||||
2
.github/workflows/translations.yml
vendored
2
.github/workflows/translations.yml
vendored
@@ -50,7 +50,7 @@ jobs:
|
||||
name: Approve Pull Request
|
||||
uses: juliangruber/approve-pull-request-action@c530832d4d346c597332e20e03605aa94fa150a8
|
||||
with:
|
||||
github-token: ${{ secrets.DOCUBOT_REPO_PAT }}
|
||||
github-token: ${{ secrets.GITHUB_TOKEN }}
|
||||
number: ${{ steps.pr.outputs.number }}
|
||||
- if: ${{ !steps.has-label.outputs.result }}
|
||||
name: Add automerge label
|
||||
|
||||
1
.github/workflows/triage-issue-comments.yml
vendored
1
.github/workflows/triage-issue-comments.yml
vendored
@@ -46,6 +46,7 @@ jobs:
|
||||
if: ${{ steps.is-internal-contributor.outputs.result == 'false' }}
|
||||
with:
|
||||
add-labels: 'triage'
|
||||
ignore-if-labeled: true
|
||||
- name: Triage to project board
|
||||
uses: rachmari/actions-add-new-issue-to-column@1a459ef92308ba7c9c9dc2fcdd72f232495574a9
|
||||
with:
|
||||
|
||||
1
.github/workflows/triage-pull-requests.yml
vendored
1
.github/workflows/triage-pull-requests.yml
vendored
@@ -12,6 +12,7 @@ on:
|
||||
|
||||
permissions:
|
||||
pull-requests: write
|
||||
repository-projects: write
|
||||
|
||||
jobs:
|
||||
triage_pulls:
|
||||
|
||||
@@ -60,7 +60,7 @@ jobs:
|
||||
token: ${{ secrets.DOCUBOT_REPO_PAT }}
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/update-graphql-files.yml
vendored
2
.github/workflows/update-graphql-files.yml
vendored
@@ -30,7 +30,7 @@ jobs:
|
||||
- name: Checkout
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
2
.github/workflows/yml-lint.yml
vendored
2
.github/workflows/yml-lint.yml
vendored
@@ -25,7 +25,7 @@ jobs:
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
|
||||
- name: Setup node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c
|
||||
with:
|
||||
node-version: 16.8.x
|
||||
cache: npm
|
||||
|
||||
BIN
assets/images/help/releases/delete-release-trash.png
Normal file
BIN
assets/images/help/releases/delete-release-trash.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 34 KiB |
BIN
assets/images/help/releases/draft-release-button-with-search.png
Normal file
BIN
assets/images/help/releases/draft-release-button-with-search.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 7.1 KiB |
BIN
assets/images/help/releases/edit-release-pencil.png
Normal file
BIN
assets/images/help/releases/edit-release-pencil.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 34 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 35 KiB |
BIN
assets/images/help/releases/refreshed-compare-tags.png
Normal file
BIN
assets/images/help/releases/refreshed-compare-tags.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 27 KiB |
BIN
assets/images/help/releases/refreshed-release-latest.png
Normal file
BIN
assets/images/help/releases/refreshed-release-latest.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 21 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 125 KiB |
BIN
assets/images/help/releases/release-compare-button.png
Normal file
BIN
assets/images/help/releases/release-compare-button.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 21 KiB |
BIN
assets/images/help/releases/release-compare-menu.png
Normal file
BIN
assets/images/help/releases/release-compare-menu.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 57 KiB After Width: | Height: | Size: 35 KiB |
BIN
assets/images/help/releases/release-title-old.png
Normal file
BIN
assets/images/help/releases/release-title-old.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
BIN
assets/images/help/releases/release-title.png
Normal file
BIN
assets/images/help/releases/release-title.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
BIN
assets/images/help/releases/search-releases.png
Normal file
BIN
assets/images/help/releases/search-releases.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 5.9 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 31 KiB After Width: | Height: | Size: 16 KiB |
@@ -22,7 +22,7 @@ Environments are used to describe a general deployment target like `production`,
|
||||
|
||||
You can configure environments with protection rules and secrets. When a workflow job references an environment, the job won't start until all of the environment's protection rules pass. A job also cannot access secrets that are defined in an environment until all the environment protection rules pass.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% ifversion fpt %}
|
||||
{% note %}
|
||||
|
||||
**Note:** If you don't use {% data variables.product.prodname_ghe_cloud %} and convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets. {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
|
||||
@@ -25,7 +25,11 @@ topics:
|
||||
|
||||
## Creating a workflow template
|
||||
|
||||
Workflow templates can be created by users with write access to the organization's `.github` repository. The templates can then be used by organization members who have permission to create workflows. You can share workflow templates if your organization's repository is public or if the repository is private and on an Enterprise plan.
|
||||
Workflow templates can be created by users with write access to the organization's `.github` repository. The templates can then be used by organization members who have permission to create workflows.
|
||||
|
||||
{% ifversion fpt %}
|
||||
Your workflow templates can be used to create workflows in public repositories only. Organizations using {% data variables.product.prodname_ghe_cloud %} can also use workflow templates to create workflows in private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/learn-github-actions/creating-workflow-templates).
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
|
||||
{% note %}
|
||||
|
||||
@@ -373,10 +373,12 @@ If you need to find the unique identifier of a job running in a workflow run, yo
|
||||
|
||||
## `jobs.<job_id>`
|
||||
|
||||
Each job must have an id to associate with the job. The key `job_id` is a string and its value is a map of the job's configuration data. You must replace `<job_id>` with a string that is unique to the `jobs` object. The `<job_id>` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
|
||||
Create an identifier for your job by giving it a unique name. The key `job_id` is a string and its value is a map of the job's configuration data. You must replace `<job_id>` with a string that is unique to the `jobs` object. The `<job_id>` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
|
||||
|
||||
### Example
|
||||
|
||||
In this example, two jobs have been created, and their `job_id` values are `my_first_job` and `my_second_job`.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
my_first_job:
|
||||
@@ -420,7 +422,7 @@ jobs:
|
||||
job2:
|
||||
needs: job1
|
||||
job3:
|
||||
if: always()
|
||||
if: {% raw %}${{ always() }}{% endraw %}
|
||||
needs: [job1, job2]
|
||||
```
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ shortTitle: Add a status badge
|
||||
You reference the workflow by the name of your workflow file.
|
||||
|
||||
```markdown
|
||||
|
||||
|
||||
```
|
||||
## Using the workflow file name
|
||||
|
||||
|
||||
@@ -24,7 +24,9 @@ When you enable {% data variables.product.prodname_GH_advanced_security %} for y
|
||||
When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features. {% ifversion ghes = 3.0 %}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)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes > 2.22 %}
|
||||
For guidance on a phased deployment of GitHub Advanced Security, see "[Deploying GitHub Advanced Security in your enterprise](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)."
|
||||
{% endif %}
|
||||
|
||||
## Prerequisites for enabling {% data variables.product.prodname_GH_advanced_security %}
|
||||
|
||||
|
||||
@@ -624,6 +624,31 @@ A `top`-like interface for current Git operations.
|
||||
ghe-btop [ <port number> | --help | --usage ]
|
||||
```
|
||||
|
||||
#### ghe-governor
|
||||
|
||||
This utility helps to analyze Git traffic. It queries _Governor_ data files, located under `/data/user/gitmon`. {% data variables.product.company_short %} holds one hour of data per file, retained for two weeks. For more information, see [Analyzing Git traffic using Governor](https://github.community/t/analyzing-git-traffic-using-governor/13516) in {% data variables.product.prodname_gcf %}.
|
||||
|
||||
```bash
|
||||
ghe-governor <subcommand> <column> [options]
|
||||
```
|
||||
|
||||
```
|
||||
ghe-governor -h
|
||||
Usage: ghe-governor [-h] <subcommand> args
|
||||
|
||||
OPTIONS:
|
||||
-h | --help Show this message.
|
||||
|
||||
Valid subcommands are:
|
||||
aggregate Find the top (n) groups of queries for a grouping function and metric
|
||||
health Summarize all recent activity on one or more servers
|
||||
top Find the top (n) queries for a given metric
|
||||
dump Dump individual operations
|
||||
test-quotas Check quota information
|
||||
|
||||
Try ghe-governor <subcommand> --help for more information on the arguments each subcommand takes.
|
||||
```
|
||||
|
||||
### ghe-repo
|
||||
|
||||
This utility allows you to change to a repository's directory and open an interactive shell as the `git` user. You can perform manual inspection or maintenance of a repository via commands like `git-*` or `git-nw-*`.
|
||||
|
||||
@@ -21,6 +21,7 @@ redirect_from:
|
||||
- /github/articles/verifying-your-enterprise-accounts-domain
|
||||
- /early-access/github/articles/verifying-your-enterprise-accounts-domain
|
||||
- /github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account
|
||||
- /admin/policies/verifying-or-approving-a-domain-for-your-enterprise
|
||||
---
|
||||
|
||||
## About verification of domains
|
||||
|
||||
@@ -24,7 +24,14 @@ The time required to failover depends on how long it takes to manually promote t
|
||||
```shell
|
||||
$ ghe-maintenance -s
|
||||
```
|
||||
2. When the number of active Git operations reaches zero, wait 30 seconds.
|
||||
2. When the number of active Git operations, MySQL queries, and Resque jobs reaches zero, wait 30 seconds.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Nomad will always have jobs running, even in maintenance mode, so you can safely ignore these jobs.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
3. To verify all replication channels report `OK`, use the `ghe-repl-status -vv` command.
|
||||
```shell
|
||||
$ ghe-repl-status -vv
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: About upgrades to new releases
|
||||
shortTitle: About upgrades
|
||||
intro: '{% ifversion ghae %}Your {% data variables.product.product_name %} enterprise is updated with the latest features and bug fixes on a regular basis by {% data variables.product.company_short %}.{% else %}You can benefit from new features and bug fixes for {% data variables.product.product_name %} by upgrading your enterprise to a newly released version.{% endif %}'
|
||||
intro: '{% ifversion ghae %}Your enterprise on {% data variables.product.product_name %} is updated with the latest features and bug fixes on a regular basis by {% data variables.product.company_short %}.{% else %}You can benefit from new features and bug fixes for {% data variables.product.product_name %} by upgrading your enterprise to a newly released version.{% endif %}'
|
||||
versions:
|
||||
ghes: '>=3.0'
|
||||
ghae: '*'
|
||||
@@ -11,13 +11,13 @@ topics:
|
||||
- Upgrades
|
||||
---
|
||||
|
||||
{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} is a fully managed service, so {% data variables.product.company_short %} completes the upgrade process for your enterprise.{% endif %}
|
||||
{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through feature and patch releases. {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} is a fully managed service, so {% data variables.product.company_short %} completes the upgrade process for your enterprise.{% endif %}
|
||||
|
||||
Major releases include new functionality and feature upgrades and typically occur quarterly. {% ifversion ghae %}{% data variables.product.company_short %} will upgrade your enterprise to the latest major release. You will be given advance notice of any planned downtime for your enterprise.{% endif %}
|
||||
Feature releases include new functionality and feature upgrades and typically occur quarterly. {% ifversion ghae %}{% data variables.product.company_short %} will upgrade your enterprise to the latest feature release. You will be given advance notice of any planned downtime for your enterprise.{% endif %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
Starting with {% data variables.product.prodname_ghe_server %} 3.0, all major releases begin with at least one release candidate. Release candidates are proposed major releases, with a complete feature set. There may be bugs or issues in a release candidate which can only be found through feedback from customers actually using {% data variables.product.product_name %}.
|
||||
Starting with {% data variables.product.prodname_ghe_server %} 3.0, all feature releases begin with at least one release candidate. Release candidates are proposed feature releases, with a complete feature set. There may be bugs or issues in a release candidate which can only be found through feedback from customers actually using {% data variables.product.product_name %}.
|
||||
|
||||
You can get early access to the latest features by testing a release candidate as soon as the release candidate is available. You can upgrade to a release candidate from a supported version and can upgrade from the release candidate to later versions when released. You should upgrade any environment running a release candidate as soon as the release is generally available. For more information, see "[Upgrade requirements](/admin/enterprise-management/upgrade-requirements)."
|
||||
|
||||
@@ -29,13 +29,13 @@ We'll use your feedback to apply bug fixes and any other necessary changes to cr
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: The upgrade to a new major release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. You can inform your users about downtime by publishing a global announcement banner, using your enterprise settings or the REST API. For more information, see "[Customizing user messages on your instance](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" and "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)."
|
||||
**Warning**: The upgrade to a new feature release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. You can inform your users about downtime by publishing a global announcement banner, using your enterprise settings or the REST API. For more information, see "[Customizing user messages on your instance](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" and "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)."
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
Minor releases, which consist of hot patches and bug fixes only, happen more frequently. Minor releases are generally available when first released, with no release candidates. Upgrading to a minor release typically requires less than five minutes of downtime.
|
||||
Patch releases, which consist of hot patches and bug fixes only, happen more frequently. Patch releases are generally available when first released, with no release candidates. Upgrading to a patch release typically requires less than five minutes of downtime.
|
||||
|
||||
To upgrade your enterprise to a new release, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)."
|
||||
|
||||
|
||||
@@ -21,6 +21,8 @@ topics:
|
||||
|
||||
The root filesystem is included in the distributed machine image. It contains the base operating system and the {% data variables.product.prodname_ghe_server %} application environment. The root filesystem should be treated as ephemeral. Any data on the root filesystem will be replaced when upgrading to future {% data variables.product.prodname_ghe_server %} releases.
|
||||
|
||||
The root storage volume is split into two equally-sized partitions. One of the partitions will be mounted as the root filesystem (`/`). The other partition is only mounted during upgrades and rollbacks of upgrades as `/mnt/upgrade`, to facilitate easier rollbacks if necessary. For example, if a 200GB root volume is allocated, there will be 100GB allocated to the root filesystem and 100GB reserved for the upgrades and rollbacks.
|
||||
|
||||
The root filesystem contains:
|
||||
- Custom certificate authority (CA) certificates (in */usr/local/share/ca-certificates*)
|
||||
- Custom networking configurations
|
||||
|
||||
@@ -128,7 +128,7 @@ You can also configure allowed IP addresses for an individual organization. For
|
||||
|
||||
## Managing SSH certificate authorities for your enterprise
|
||||
|
||||
You can use a SSH certificate authorities (CA) to allow members of any organization owned by your enterprise to access that organization's repositories using SSH certificates you provide. {% data reusables.organizations.can-require-ssh-cert %} For more information, see "[About SSH certificate authorities](http://localhost:4000/en/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)."
|
||||
You can use a SSH certificate authorities (CA) to allow members of any organization owned by your enterprise to access that organization's repositories using SSH certificates you provide. {% data reusables.organizations.can-require-ssh-cert %} For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)."
|
||||
|
||||
### Adding an SSH certificate authority
|
||||
|
||||
|
||||
@@ -4,6 +4,7 @@ intro: 'You can set policies in {% data variables.product.product_name %} to red
|
||||
redirect_from:
|
||||
- /enterprise/admin/developer-workflow
|
||||
- /enterprise/admin/policies
|
||||
- /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -44,7 +44,7 @@ If your enterprise uses {% data variables.product.prodname_emus %}, enterprise o
|
||||
|
||||
## {% ifversion ghec %}Inviting{% elsif ghes %}Adding{% endif %} an enterprise administrator to your enterprise account
|
||||
|
||||
{% ifversion ghec %}After you invite someone to join the enterprise account, they must accept the emailed invitation before they can access the enterprise account.{% endif %}
|
||||
{% ifversion ghec %}After you invite someone to join the enterprise account, they must accept the emailed invitation before they can access the enterprise account. Pending invitations will expire after 7 days.{% endif %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.people-tab %}
|
||||
|
||||
@@ -22,7 +22,9 @@ shortTitle: Import to your enterprise
|
||||
---
|
||||
## Applying the imported data on {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
Once you have [prepared your migration](/admin/user-management/preparing-to-migrate-data-to-your-enterprise) you can use the following steps to complete the migration.
|
||||
Before you can migrate data to your enterprise, you must prepare the data and resolve any conflicts. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)."
|
||||
|
||||
After you prepare the data and resolve conflicts, you can apply the imported data on {% data variables.product.product_name %}.
|
||||
|
||||
{% data reusables.enterprise_installation.ssh-into-target-instance %}
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ To maintain account security, you can regularly review your SSH keys list and re
|
||||
If you haven't used your SSH key for a year, then {% data variables.product.prodname_dotcom %} will automatically delete your inactive SSH key as a security precaution. For more information, see "[Deleted or missing SSH keys](/articles/deleted-or-missing-ssh-keys)."
|
||||
{% endif %}
|
||||
|
||||
If you're a member of an organization that provides SSH certificates, you can use your certificate to access that organization's repositories without adding the certificate to your account on {% data variables.product.product_location %}. For more information, see "[About SSH certificate authorities](/articles/about-ssh-certificate-authorities)."
|
||||
If you're a member of an organization that provides SSH certificates, you can use your certificate to access that organization's repositories without adding the certificate to your account on {% data variables.product.product_name %}. You cannot use your certificate to access forks of the organization's repositories that are owned by your user account. For more information, see "[About SSH certificate authorities](/articles/about-ssh-certificate-authorities)."
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@ topics:
|
||||
|
||||
{% data variables.product.prodname_codespaces %} usage is billed according to the units of measure in the following table:
|
||||
|
||||
Product | SKU | Unit of measure | Price |
|
||||
| Product | SKU | Unit of measure | Price |
|
||||
| ------------------- | -------- | --------------- | ----- |
|
||||
| Codespaces Compute | 2 core | 1 hour | $0.18 |
|
||||
| | 4 core | 1 hour | $0.36 |
|
||||
|
||||
@@ -54,7 +54,7 @@ Each user on {% data variables.product.product_location %} consumes a seat on yo
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.billing.about-invoices-for-enterprises %} For more information about usage and invoices, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" and {% ifversion ghes %}"<a href="/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise" class="dotcom-only">Managing invoices for your enterprise</a>" in the {% data variables.product.prodname_dotcom_the_website %} documentation.{% elsif ghec %}"[Managing invoices for your enterprise](/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)."{% endif %}
|
||||
{% data reusables.billing.about-invoices-for-enterprises %} For more information about usage and invoices, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" and {% ifversion ghes %}"[Managing invoices for your enterprise](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% elsif ghec %}"[Managing invoices for your enterprise](/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)."{% endif %}
|
||||
|
||||
Administrators for your enterprise account on {% data variables.product.prodname_dotcom_the_website %} can access and manage billing for the enterprise.
|
||||
|
||||
|
||||
@@ -18,6 +18,12 @@ After you purchase or upgrade a license for {% data variables.product.prodname_e
|
||||
|
||||
## Uploading your license to {% data variables.product.product_location_enterprise %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Updating your license causes a small amount of downtime for {% data variables.product.product_location %}.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
1. Sign into {% data variables.product.product_location_enterprise %} as a site administrator.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
|
||||
@@ -24,7 +24,7 @@ You can view license usage for your enterprise account on {% data variables.prod
|
||||
|
||||
You can view license usage for {% data variables.product.prodname_ghe_server %} on {% data variables.product.product_location %}.
|
||||
|
||||
{% data reusables.enterprise-licensing.you-can-sync-for-a-combined-view %} For more information about the display of license usage on {% data variables.product.prodname_dotcom_the_website %}, see "<a href="/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise" class="dotcom-only">Viewing license usage for {% data variables.product.prodname_enterprise %}</a>" in the {% data variables.product.prodname_dotcom_the_website %} documentation.
|
||||
{% data reusables.enterprise-licensing.you-can-sync-for-a-combined-view %} For more information about the display of license usage on {% data variables.product.prodname_dotcom_the_website %}, see "[Viewing license usage for {% data variables.product.prodname_enterprise %}](/enterprise-cloud@latest/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -30,7 +30,7 @@ topics:
|
||||
|
||||
SARIF (Static Analysis Results Interchange Format) is an [OASIS Standard](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html) that defines an output file format. The SARIF standard is used to streamline how static analysis tools share their results. {% data variables.product.prodname_code_scanning_capc %} supports a subset of the SARIF 2.1.0 JSON schema.
|
||||
|
||||
To upload a SARIF file from a third-party static code analysis engine, you'll need to ensure that uploaded files use the SARIF 2.1.0 version. {% data variables.product.prodname_dotcom %} will parse the SARIF file and show alerts using the results in your repository as a part of the {% data variables.product.prodname_code_scanning %} experience. For more information, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github)." For more information about the SARIF 2.1.0 JSON schema, see [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json).
|
||||
To upload a SARIF file from a third-party static code analysis engine, you'll need to ensure that uploaded files use the SARIF 2.1.0 version. {% data variables.product.prodname_dotcom %} will parse the SARIF file and show alerts using the results in your repository as a part of the {% data variables.product.prodname_code_scanning %} experience. For more information, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github)." For more information about the SARIF 2.1.0 JSON schema, see [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/CommitteeSpecifications/2.1.0/sarif-schema-2.1.0.json).
|
||||
|
||||
If you're using {% data variables.product.prodname_actions %} with the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %}, then the {% data variables.product.prodname_code_scanning %} results will automatically use the supported subset of SARIF 2.1.0. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
|
||||
|
||||
|
||||
@@ -63,7 +63,7 @@ For information about permission requirements for actions related to {% data var
|
||||
{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)."
|
||||
{% endif %}
|
||||
|
||||
When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} may also notify the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)."
|
||||
When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it {% ifversion fpt or ghec or ghes > 3.0 %} on the Security tab for the repository and{% endif %} in the repository's dependency graph. The alert includes {% ifversion fpt or ghec or ghes > 3.0 %}a link to the affected file in the project, and {% endif %}information about a fixed version. {% data variables.product.product_name %} may also notify the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
|
||||
|
||||
@@ -28,6 +28,8 @@ GitHub maintains an official list of recommended *.gitignore* files for many pop
|
||||
$ touch .gitignore
|
||||
```
|
||||
|
||||
If the command succeeds, there will be no output.
|
||||
|
||||
For an example *.gitignore* file, see "[Some common .gitignore configurations](https://gist.github.com/octocat/9257657)" in the Octocat repository.
|
||||
|
||||
If you want to ignore a file that is already checked in, you must untrack the file before you add a rule to ignore it. From your terminal, untrack the file.
|
||||
|
||||
@@ -100,7 +100,7 @@ By default, everyone in an enterprise is a member of the enterprise. There are a
|
||||
#### 2. Inviting people to manage your enterprise
|
||||
You can invite people to manage your enterprise as enterprise owners or billing managers, as well as remove those who no longer need access. For more information, see "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)."
|
||||
|
||||
You can also grant enterprise members the ability to manage support tickets in the support portal. For more information, see "[Managing support entitlements for your enterprise](/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
|
||||
You can also grant enterprise members the ability to manage support tickets in the support portal. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
|
||||
#### 3. Viewing people in your enterprise
|
||||
To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)."
|
||||
|
||||
@@ -178,7 +178,7 @@ To manage and moderate your enterprise, you can set policies for organizations w
|
||||
|
||||
You can choose to enforce a number of policies for all organizations owned by your enterprise, or choose to allow these policies to be set in each organization. Types of policies you can enforce include repository management, project board, and team policies. For more information, see "[Setting policies for your enterprise](/enterprise-cloud@latest/admin/policies)."
|
||||
#### 2. Viewing audit logs, configuring webhooks, and restricting email notifications for your enterprise
|
||||
You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Viewing the audit logs for organizations in your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise)" and "[Managing global webhooks](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks)."
|
||||
You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Viewing the audit logs for organizations in your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise)" and "[Managing global webhooks](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks)."
|
||||
|
||||
You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. For more information, see "[Restricting email notifications for your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."
|
||||
|
||||
|
||||
@@ -47,17 +47,20 @@ Below is a list of some of the available keyboard shortcuts.
|
||||
|<kbd>.</kbd>| Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
|
||||
| <kbd>control b</kbd> or <kbd>command b</kbd> | Inserts Markdown formatting for bolding text
|
||||
| <kbd>control i</kbd> or <kbd>command i</kbd> | Inserts Markdown formatting for italicizing text
|
||||
| <kbd>control k</kbd> or <kbd>command k</kbd> | Inserts Markdown formatting for creating a link
|
||||
| <kbd>control k</kbd> or <kbd>command k</kbd> | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae-next or ghes > 3.3 %}
|
||||
| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd> | Inserts Markdown formatting for an ordered list
|
||||
| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd> | Inserts Markdown formatting for an unordered list
|
||||
| <kbd>control shift .</kbd> or <kbd>command shift.</kbd> | Inserts Markdown formatting for a quote{% endif %}
|
||||
|<kbd>e</kbd> | Open source code file in the **Edit file** tab
|
||||
|<kbd>control f</kbd> or <kbd>command f</kbd> | Start searching in file editor
|
||||
|<kbd>control g</kbd> or <kbd>command g</kbd> | Find next
|
||||
|<kbd>shift control g</kbd> or <kbd>shift command g</kbd> | Find previous
|
||||
|<kbd>shift control f</kbd> or <kbd>command option f</kbd> | Replace
|
||||
|<kbd>shift control r</kbd> or <kbd>shift command option f</kbd> | Replace all
|
||||
|<kbd>control shift g</kbd> or <kbd>command shift g</kbd> | Find previous
|
||||
|<kbd>control shift f</kbd> or <kbd>command option f</kbd> | Replace
|
||||
|<kbd>control shift r</kbd> or <kbd>command shift option f</kbd> | Replace all
|
||||
|<kbd>alt g</kbd> | Jump to line
|
||||
|<kbd>control z</kbd> or <kbd>command z</kbd> | Undo
|
||||
|<kbd>control y</kbd> or <kbd>command y</kbd> | Redo
|
||||
|<kbd>cmd + shift + p</kbd> | Toggles between the **Edit file** and **Preview changes** tabs
|
||||
|<kbd>command shift p</kbd> | Toggles between the **Edit file** and **Preview changes** tabs
|
||||
|<kbd>control s</kbd> or <kbd>command s</kbd> | Write a commit message
|
||||
|
||||
For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirror.net/doc/manual.html#commands).
|
||||
|
||||
@@ -18,7 +18,7 @@ redirect_from:
|
||||
|
||||
SARIF (Static Analysis Results Interchange Format) is an [OASIS Standard](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html) that defines an output file format. The SARIF standard is used to streamline how static analysis tools share their results. {% data variables.product.prodname_code_scanning_capc %} supports a subset of the SARIF 2.1.0 JSON schema.
|
||||
|
||||
To upload a SARIF file from a third-party static code analysis engine, you'll need to ensure that uploaded files use the SARIF 2.1.0 version. {% data variables.product.prodname_dotcom %} will parse the SARIF file and show alerts using the results in your repository as a part of the {% data variables.product.prodname_code_scanning %} experience. For more information, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)." For more information about the SARIF 2.1.0 JSON schema, see [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json).
|
||||
To upload a SARIF file from a third-party static code analysis engine, you'll need to ensure that uploaded files use the SARIF 2.1.0 version. {% data variables.product.prodname_dotcom %} will parse the SARIF file and show alerts using the results in your repository as a part of the {% data variables.product.prodname_code_scanning %} experience. For more information, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)." For more information about the SARIF 2.1.0 JSON schema, see [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/CommitteeSpecifications/2.1.0/sarif-schema-2.1.0.json).
|
||||
|
||||
If you're using {% data variables.product.prodname_actions %} with the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %}, then the {% data variables.product.prodname_code_scanning %} results will automatically use the supported subset of SARIF 2.1.0. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)."
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@ topics:
|
||||
{% ifversion fpt or ghec %}
|
||||
Enterprise owners on {% data variables.product.prodname_dotcom_the_website %} can now find documentation about enterprise management in the new {% data variables.product.prodname_ghe_cloud %} version of "[Enterprise administrators]({% ifversion fpt or ghec %}/enterprise-cloud@latest{% endif %}/admin#all-docs)."
|
||||
|
||||
For more information about the {% data variables.product.prodname_ghe_cloud %} version of GitHub Docs, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-10-15-ghec-version-docs/).
|
||||
For more information about the {% data variables.product.prodname_ghe_cloud %} version of GitHub Docs, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-10-15-github-enterprise-cloud-version-for-github-docs/).
|
||||
{% else %}
|
||||
Enterprise owners on {% data variables.product.product_name %} can now find documentation about enterprise management in "[Enterprise administrators](/admin#all-docs)."
|
||||
{% endif %}
|
||||
|
||||
@@ -270,12 +270,27 @@ You can add footnotes to your content by using this bracket syntax:
|
||||
```
|
||||
Here is a simple footnote[^1].
|
||||
|
||||
A footnote can also have multiple lines[^2].
|
||||
|
||||
You can also use words, to fit your writing style more closely[^note].
|
||||
|
||||
[^1]: My reference.
|
||||
[^2]: Every new line should be prefixed with 2 spaces.
|
||||
This allows you to have a footnote with multiple lines.
|
||||
[^note]:
|
||||
Named footnotes will still render with numbers instead of the text but allow easier identification and linking.
|
||||
This footnote also has been made with a different syntax using 4 spaces for new lines.
|
||||
```
|
||||
|
||||
The footnote will render like this:
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Note**: The position of a footnote in your Markdown does not influence where the footnote will be rendered. You can write a footnote right after your reference to the footnote, and the footnote will still render at the bottom of the Markdown.
|
||||
|
||||
{% endtip %}
|
||||
{% endif %}
|
||||
|
||||
## Hiding content with comments
|
||||
|
||||
@@ -148,5 +148,5 @@ To delete a view:
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)
|
||||
- "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project)
|
||||
- "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)"
|
||||
- "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project)"
|
||||
|
||||
@@ -123,7 +123,7 @@ Using the qualifier `country`, you can filter events in the audit log based on t
|
||||
You can interact with the audit log using the GraphQL API{% ifversion fpt or ghec %} or the REST API{% endif %}.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
The audit log API requires {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
The audit log API requires {% data variables.product.prodname_ghe_cloud %}.{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %}
|
||||
|
||||
### Using the GraphQL API
|
||||
|
||||
|
||||
@@ -27,7 +27,7 @@ If your organization [requires members and outside collaborators to use two-fact
|
||||
|
||||
{% data reusables.organizations.outside_collaborator_forks %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% ifversion fpt %}
|
||||
To further support your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like protected branches and code owners on private repositories. {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -43,7 +43,7 @@ In addition to managing organization-level settings, organization owners have ad
|
||||
|
||||
## Repository access for each permission level
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% ifversion fpt %}
|
||||
Some of the features listed below are limited to organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -22,6 +22,8 @@ After you add an SSH CA to your organization or enterprise account, you can use
|
||||
|
||||
For example, you can build an internal system that issues a new certificate to your developers every morning. Each developer can use their daily certificate to work on your organization's repositories on {% data variables.product.product_name %}. At the end of the day, the certificate can automatically expire, protecting your repositories if the certificate is later compromised.
|
||||
|
||||
Members will not be able to use their certificates to access forks of your repositories that are owned by their user accounts.
|
||||
|
||||
When you issue each certificate, you must include an extension that specifies which {% data variables.product.product_name %} user the certificate is for. For example, you can use OpenSSH's `ssh-keygen` command, replacing _KEY-IDENTITY_ with your key identity and _USERNAME_ with a {% data variables.product.product_name %} username. The certificate you generate will be authorized to act on behalf of that user for any of your organization's resources. Make sure you validate the user's identity before you issue the certificate.
|
||||
|
||||
```shell
|
||||
|
||||
@@ -14,10 +14,16 @@ topics:
|
||||
shortTitle: Create accounts for people
|
||||
---
|
||||
|
||||
Because you access an organization by logging in to a personal account, each of your team members needs a personal account. Once you have user names for each person you'd like to add to your organization, you can add them to teams.
|
||||
## About user accounts
|
||||
|
||||
Because you access an organization by logging in to a user account, each of your team members needs to create their own user account. After you have usernames for each person you'd like to add to your organization, you can add the users to teams.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
If you need greater control over the user accounts of your organization members, consider {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %}
|
||||
{% endif %}
|
||||
|
||||
## Adding users to your organization
|
||||
|
||||
1. Provide each person instructions to [create a personal account](/articles/signing-up-for-a-new-github-account).
|
||||
1. Provide each person instructions to [create a user account](/articles/signing-up-for-a-new-github-account).
|
||||
2. Ask for the username of each person you want to give organization membership to.
|
||||
3. [Invite the new personal accounts to join](/articles/inviting-users-to-join-your-organization) your organization. Use [organization roles](/articles/permission-levels-for-an-organization) and [repository permissions](/articles/repository-permission-levels-for-an-organization) to limit the access of each account.
|
||||
|
||||
@@ -29,7 +29,7 @@ After verifying ownership of your organization's domains, a "Verified" badge wil
|
||||
|
||||
{% data reusables.organizations.verified-domains-details %}
|
||||
|
||||
{% ifversion fpt or ghec %}On {% data variables.product.prodname_ghe_cloud %}, after verifying ownership of your organization's domain, you can restrict email notifications for the organization to that domain. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)." {% data reusables.enterprise.link-to-ghec-trial %}{% endif %}
|
||||
{% ifversion fpt or ghec %}On {% data variables.product.prodname_ghe_cloud %}, after verifying ownership of your organization's domain, you can restrict email notifications for the organization to that domain. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)." {% ifversion fpt %}{% data reusables.enterprise.link-to-ghec-trial %}{% endif %}{% endif %}
|
||||
|
||||
## About domain approval
|
||||
|
||||
|
||||
@@ -26,7 +26,7 @@ Organization members can have *owner*{% ifversion fpt or ghec %}, *billing manag
|
||||
{% endif %}
|
||||
- **Members** are the default role for everyone else.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% ifversion fpt %}
|
||||
Some of the features listed below are limited to organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ shortTitle: IAM with SAML SSO
|
||||
|
||||
Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
|
||||
|
||||
{% data reusables.saml.saml-requires-ghec %} {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
{% data reusables.saml.saml-requires-ghec %}{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %}
|
||||
|
||||
{% data reusables.saml.outside-collaborators-exemption %}
|
||||
|
||||
@@ -36,7 +36,7 @@ Members must periodically authenticate with your IdP to authenticate and gain ac
|
||||
|
||||
To access the organization's protected resources using the API and Git on the command line, members must authorize and authenticate with a personal access token or SSH key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."
|
||||
|
||||
The first time a member uses SAML SSO to access your organization, {% data variables.product.prodname_dotcom %} automatically creates a record that links your organization, the member's account on {% data variables.product.product_location %}, and the member's account on your IdP. You can view and revoke the linked SAML identity, active sessions, and authorized credentials for members of your organization or enterprise account. For more information, 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 account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)."
|
||||
The first time a member uses SAML SSO to access your organization, {% data variables.product.prodname_dotcom %} automatically creates a record that links your organization, the member's account on {% data variables.product.product_location %}, and the member's account on your IdP. You can view and revoke the linked SAML identity, active sessions, and authorized credentials for members of your organization or enterprise account. For more information, 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 account](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)."
|
||||
|
||||
If members are signed in with a SAML SSO session when they create a new repository, the default visibility of that repository is private. Otherwise, the default visibility is public. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ If you enable but don't enforce SAML SSO, organization members who choose not to
|
||||
|
||||
## Enabling and testing SAML single sign-on for your organization
|
||||
|
||||
{% data reusables.saml.saml-requires-ghec %} {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
{% data reusables.saml.saml-requires-ghec %}{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %}
|
||||
|
||||
Before your enforce SAML SSO in your organization, ensure that you've prepared the organization. For more information, see "[Preparing to enforce SAML single sign-on in your organization](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)."
|
||||
|
||||
|
||||
@@ -37,6 +37,8 @@ You can also use LDAP Sync to synchronize {% data variables.product.product_loca
|
||||
|
||||
{% data reusables.organizations.types-of-team-visibility %}
|
||||
|
||||
You can view all the teams you belong to on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)."
|
||||
|
||||
## Team pages
|
||||
|
||||
Each team has its own page within an organization. On a team's page, you can view team members, child teams, and the team's repositories. Organization owners and team maintainers can access team settings and update the team's description and profile picture from the team's page.
|
||||
|
||||
@@ -22,7 +22,7 @@ By using code review assignments, any time your team has been requested to revie
|
||||
|
||||
When code owners are automatically requested for review, the team is still removed and replaced with individuals. The individual approvals don't satisfy the requirement for code owner approval in a protected branch. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% ifversion fpt %}
|
||||
To further enhance your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like protected branches and code owners on private repositories. {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -26,7 +26,9 @@ When {% data variables.product.prodname_oauth_app %} access restrictions are ena
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% ifversion fpt %}
|
||||
To further protect your organization's resources, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes security features like SAML single sign-on. {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
{% endif %}
|
||||
|
||||
## Setting up {% data variables.product.prodname_oauth_app %} access restrictions
|
||||
|
||||
|
||||
@@ -65,7 +65,7 @@ If your instance has subdomain isolation enabled:
|
||||
</repository>
|
||||
<repository>
|
||||
<id>github</id>
|
||||
<url>https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/*</url>
|
||||
<url>https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY</url>
|
||||
<snapshots>
|
||||
<enabled>true</enabled>
|
||||
</snapshots>
|
||||
@@ -107,7 +107,7 @@ If your instance has subdomain isolation disabled:
|
||||
</repository>
|
||||
<repository>
|
||||
<id>github</id>
|
||||
<url>HOSTNAME/_registry/maven/OWNER/*</url>
|
||||
<url>HOSTNAME/_registry/maven/OWNER/REPOSITORY</url>
|
||||
<snapshots>
|
||||
<enabled>true</enabled>
|
||||
</snapshots>
|
||||
|
||||
@@ -71,7 +71,15 @@ People with admin permissions for a repository can change an existing repository
|
||||
|
||||
{% data reusables.repositories.about-internal-repos %} For more information on innersource, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
|
||||
|
||||
People who are members of an organization within the enterprise have read permissions to internal repositories, but internal repositories are not visible to people {% ifversion fpt or ghec %}outside of the enterprise{% else %}who are not members of an organization{% endif %}, including outside collaborators on organization repositories. For more information, see {% ifversion fpt or ghae or ghec %}"[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)" and {% endif %}"[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)."
|
||||
All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people {% ifversion fpt or ghec %}outside of the enterprise{% else %}who are not members of any organization{% endif %}, including outside collaborators on organization repositories. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" and "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)."
|
||||
|
||||
{% ifversion ghes %}
|
||||
{% note %}
|
||||
|
||||
**Note:** A user must be part of an organization to be an enterprise member and have access to internal repositories. If a user on {% data variables.product.product_location %} is not a member of any organization, that user will not have access to internal repositories.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.repositories.internal-repo-default %}
|
||||
|
||||
|
||||
@@ -26,8 +26,8 @@ topics:
|
||||
|
||||
When you transfer a repository to a new owner, they can immediately administer the repository's contents, issues, pull requests, releases, project boards, and settings.
|
||||
|
||||
Prerequisites for repository transfers: {% ifversion fpt or ghec %}
|
||||
- When you transfer a repository that you own to another user account, the new owner will receive a confirmation email. The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %}
|
||||
Prerequisites for repository transfers:
|
||||
- When you transfer a repository that you own to another user account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %}
|
||||
- To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization.
|
||||
- The target account must not have a repository with the same name, or a fork in the same network.
|
||||
- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.
|
||||
|
||||
@@ -48,7 +48,7 @@ Alternatively, you can enable {% data variables.product.prodname_actions %} in y
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 2.22 or ghae-next or ghec %}
|
||||
{% ifversion fpt or ghec or ghes > 2.22 or ghae %}
|
||||
|
||||
## Managing {% data variables.product.prodname_actions %} permissions for your repository
|
||||
|
||||
@@ -100,7 +100,8 @@ You can configure this behavior for a repository using the procedure below. Modi
|
||||
{% data reusables.actions.workflow-run-approve-link %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 2.22 or ghec %}
|
||||
{% ifversion fpt or ghec or ghes > 2.22 or ghae %}
|
||||
|
||||
## Enabling workflows for private repository forks
|
||||
|
||||
{% data reusables.github-actions.private-repository-forks-overview %}
|
||||
|
||||
@@ -19,7 +19,9 @@ topics:
|
||||
---
|
||||
## About releases
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4972 or ghec %}
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
|
||||
|
||||
{% elsif ghes > 3.2 or ghae-issue-4972 %}
|
||||
|
||||
{% else %}
|
||||
|
||||
|
||||
@@ -13,12 +13,6 @@ communityRedirect:
|
||||
href: 'https://github.com/github/feedback/discussions/categories/releases-feedback'
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data reusables.repositories.auto-gen-release-public-beta %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## About automatically generated release notes
|
||||
|
||||
Automatically generated release notes provide an automated alternative to manually writing release notes for your {% data variables.product.prodname_dotcom %} releases. With automatically generated release notes, you can quickly generate an overview of the contents of a release. You can also customize your automated release notes, using labels to create custom categories to organize pull requests you want to include, and exclude certain labels and users from appearing in the output.
|
||||
|
||||
@@ -16,6 +16,14 @@ redirect_from:
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.releases %}
|
||||
3. Next to the release you want to use as your base, click **Compare**.
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
4. Use the "Compare" drop-down menu and select the tags you want to compare.
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
@@ -16,6 +16,7 @@ children:
|
||||
- /about-releases
|
||||
- /managing-releases-in-a-repository
|
||||
- /viewing-your-repositorys-releases-and-tags
|
||||
- /searching-a-repositorys-releases
|
||||
- /linking-to-releases
|
||||
- /comparing-releases
|
||||
- /automatically-generated-release-notes
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user