diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json index 73ce92bf2d..10410cf645 100644 --- a/.devcontainer/devcontainer.json +++ b/.devcontainer/devcontainer.json @@ -17,7 +17,8 @@ // Install features. Type 'feature' in the VS Code command palette for a full list. "features": { - "git-lfs": "latest" + "git-lfs": "latest", + "sshd": "latest" }, // Visual Studio Code extensions which help authoring for docs.github.com. diff --git a/.github/actions-scripts/content-changes-table-comment.js b/.github/actions-scripts/content-changes-table-comment.js index 4aecea4709..32400b46c8 100755 --- a/.github/actions-scripts/content-changes-table-comment.js +++ b/.github/actions-scripts/content-changes-table-comment.js @@ -2,6 +2,7 @@ import * as github from '@actions/github' import { setOutput } from '@actions/core' +import got from 'got' import { getContents } from '../../script/helpers/git-utils.js' import parse from '../../lib/read-frontmatter.js' @@ -47,6 +48,13 @@ const articleFiles = files.filter( const lines = await Promise.all( articleFiles.map(async (file) => { + // Action triggered on PR and after preview env is deployed. Check health to determine if preview env is ready (healthy) + let appUrlIsHealthy = false + try { + const res = await got.head(`${APP_URL}/healthz`, { retry: { limit: 0 } }) + appUrlIsHealthy = res.statusCode === 200 + } catch (err) {} + const sourceUrl = file.blob_url const fileName = file.filename.slice(pathPrefix.length) const fileUrl = fileName.slice(0, fileName.lastIndexOf('.')) @@ -70,7 +78,8 @@ const lines = await Promise.all( const { data } = parse(fileContents) let contentCell = '' - let previewCell = '' + let previewCell = appUrlIsHealthy ? '' : '_Deployment pending..._' + let prodCell = '' if (file.status === 'added') contentCell = 'New file: ' @@ -98,12 +107,16 @@ const lines = await Promise.all( if (versions.toString() === nonEnterpriseDefaultVersion) { // omit version from fpt url - previewCell += `[${plan}](${APP_URL}/${fileUrl})
` + previewCell += appUrlIsHealthy ? `[${plan}](${APP_URL}/${fileUrl})
` : '' prodCell += `[${plan}](${PROD_URL}/${fileUrl})
` } else { // for non-versioned releases (ghae, ghec) use full url - previewCell += `[${plan}](${APP_URL}/${versions}/${fileUrl})
` + if (appUrlIsHealthy) { + previewCell += appUrlIsHealthy + ? `[${plan}](${APP_URL}/${versions}/${fileUrl})
` + : '' + } prodCell += `[${plan}](${PROD_URL}/${versions}/${fileUrl})
` } } else if (versions.length) { @@ -113,7 +126,9 @@ const lines = await Promise.all( prodCell += `${plan}@ ` versions.forEach((version) => { - previewCell += `[${version.split('@')[1]}](${APP_URL}/${version}/${fileUrl}) ` + previewCell += appUrlIsHealthy + ? `[${version.split('@')[1]}](${APP_URL}/${version}/${fileUrl}) ` + : '' prodCell += `[${version.split('@')[1]}](${PROD_URL}/${version}/${fileUrl}) ` }) previewCell += '
' diff --git a/.github/workflows/content-changes-table-comment.yml b/.github/workflows/content-changes-table-comment.yml index 51fa2ce095..355af58d08 100644 --- a/.github/workflows/content-changes-table-comment.yml +++ b/.github/workflows/content-changes-table-comment.yml @@ -5,6 +5,10 @@ name: Content Changes Table Comment # **Who does it impact**: docs-internal/docs maintainers and contributors on: + # Trigger this workflow after preview deployment runs + workflow_run: + workflows: + - Azure - Deploy Preview Environment workflow_dispatch: pull_request_target: @@ -40,7 +44,6 @@ jobs: filters: | filterContentDir: - 'content/**/*' - filterContentDir: needs: PR-Preview-Links if: ${{ needs.PR-Preview-Links.outputs.filterContentDir == 'true' }} diff --git a/assets/images/README.md b/assets/images/README.md new file mode 100644 index 0000000000..9756be1695 --- /dev/null +++ b/assets/images/README.md @@ -0,0 +1,5 @@ +# Images +The `/assets/images` directory holds all the site's images. + + +See [imaging and versioning](https://github.com/github/docs/blob/main/contributing/images-and-versioning.md) from the contributing docs for more information. diff --git a/assets/images/help/repository/sync-fork-dropdown.png b/assets/images/help/repository/sync-fork-dropdown.png new file mode 100644 index 0000000000..d2667c981a Binary files /dev/null and b/assets/images/help/repository/sync-fork-dropdown.png differ diff --git a/assets/images/help/repository/update-branch-button.png b/assets/images/help/repository/update-branch-button.png new file mode 100644 index 0000000000..39694f5e96 Binary files /dev/null and b/assets/images/help/repository/update-branch-button.png differ diff --git a/components/context/ProductLandingContext.tsx b/components/context/ProductLandingContext.tsx index 4c61a97ded..ed3f5f0785 100644 --- a/components/context/ProductLandingContext.tsx +++ b/components/context/ProductLandingContext.tsx @@ -134,6 +134,10 @@ export const getProductLandingContextFromRequest = (req: any): ProductLandingCon .filter(([key]) => { return key === 'guides' || key === 'popular' || key === 'videos' }) + // This is currently only used to filter out videos with a blank title + // indicating that the video is not available for the currently selected + // version + .filter(([, links]: any) => links.every((link: FeaturedLink) => link.title)) .map(([key, links]: any) => { return { label: diff --git a/components/graphql/GraphqlItem.tsx b/components/graphql/GraphqlItem.tsx index eae46a7d41..49a8b0417c 100644 --- a/components/graphql/GraphqlItem.tsx +++ b/components/graphql/GraphqlItem.tsx @@ -12,7 +12,7 @@ type Props = { export function GraphqlItem({ item, heading, children, headingLevel = 2 }: Props) { const lowerCaseName = item.name.toLowerCase() return ( - <> +
{headingLevel === 2 && (

@@ -38,6 +38,6 @@ export function GraphqlItem({ item, heading, children, headingLevel = 2 }: Props {heading &&

{heading}

} {children}

- + ) } diff --git a/components/hooks/useSession.ts b/components/hooks/useSession.ts index 7bbbfaaca9..1ea66391d8 100644 --- a/components/hooks/useSession.ts +++ b/components/hooks/useSession.ts @@ -12,7 +12,6 @@ export default async function fetcher( export type Session = { isSignedIn: boolean csrfToken?: string - userLanguage: string // en, es, ja, cn } // React hook version diff --git a/components/hooks/useUserLanguage.ts b/components/hooks/useUserLanguage.ts new file mode 100644 index 0000000000..82a6a88af3 --- /dev/null +++ b/components/hooks/useUserLanguage.ts @@ -0,0 +1,28 @@ +import { useState, useEffect } from 'react' +import Cookies from 'js-cookie' + +import { languageKeys } from '../../lib/languages.js' +import { PREFERRED_LOCALE_COOKIE_NAME } from '../../lib/constants.js' + +export function useUserLanguage() { + const [userLanguage, setUserLanguage] = useState('en') + + useEffect(() => { + const languagePreferred = [ + Cookies.get(PREFERRED_LOCALE_COOKIE_NAME), + navigator.language, + ...navigator.languages, + ] + .filter(Boolean) + // If it comes from `navigator.language` it most likely will contain + // the region. E.g. `en-US` but in our application, we don't use + // the region. + .map((lang) => lang && lang.slice(0, 2).toLowerCase()) + .find((lang) => lang && languageKeys.includes(lang)) + if (languagePreferred) { + setUserLanguage(languagePreferred) + } + }, []) + + return { userLanguage } +} diff --git a/components/page-header/HeaderNotifications.tsx b/components/page-header/HeaderNotifications.tsx index e2062ee9ba..6035d1e392 100644 --- a/components/page-header/HeaderNotifications.tsx +++ b/components/page-header/HeaderNotifications.tsx @@ -6,7 +6,7 @@ import { useMainContext } from 'components/context/MainContext' import { useTranslation } from 'components/hooks/useTranslation' import { ExcludesNull } from 'components/lib/ExcludesNull' import { useVersion } from 'components/hooks/useVersion' -import { useSession } from 'components/hooks/useSession' +import { useUserLanguage } from 'components/hooks/useUserLanguage' import styles from './HeaderNotifications.module.scss' enum NotificationType { @@ -23,8 +23,7 @@ export const HeaderNotifications = () => { const router = useRouter() const { currentVersion } = useVersion() const { relativePath, allVersions, data, currentPathWithoutLanguage, page } = useMainContext() - const { session } = useSession() - const userLanguage = session?.userLanguage + const { userLanguage } = useUserLanguage() const { languages } = useLanguages() const { t } = useTranslation('header') @@ -32,9 +31,13 @@ export const HeaderNotifications = () => { const translationNotices: Array = [] if (router.locale === 'en') { if (userLanguage && userLanguage !== 'en') { + let href = `/${userLanguage}` + if (currentPathWithoutLanguage !== '/') { + href += currentPathWithoutLanguage + } translationNotices.push({ type: NotificationType.TRANSLATION, - content: `This article is also available in ${languages[userLanguage]?.name}.`, + content: `This article is also available in ${languages[userLanguage]?.name}.`, }) } } else { diff --git a/components/page-header/LanguagePicker.tsx b/components/page-header/LanguagePicker.tsx index fefcab5a91..13b9a33996 100644 --- a/components/page-header/LanguagePicker.tsx +++ b/components/page-header/LanguagePicker.tsx @@ -4,9 +4,7 @@ import Cookies from 'js-cookie' import { useLanguages } from 'components/context/LanguagesContext' import { Picker } from 'components/ui/Picker' import { useTranslation } from 'components/hooks/useTranslation' - -// This value is replicated in two places! See middleware/detect-language.js -const PREFERRED_LOCALE_COOKIE_NAME = 'preferredlang' +import { PREFERRED_LOCALE_COOKIE_NAME } from '../../lib/constants.js' type Props = { variant?: 'inline' @@ -31,6 +29,14 @@ export const LanguagePicker = ({ variant }: Props) => { function rememberPreferredLanguage(value: string) { try { + // The reason we use a cookie and not local storage is because + // this cookie value is used and needed by the server. For + // example, when doing `GET /some/page` we need the cookie + // to redirect to `Location: /ja/some/page`. + // It's important it's *not* an HttpOnly cookie because we + // need this in the client-side which is used to determine + // the UI about displaying notifications about preferred + // language if your cookie doesn't match the current URL. Cookies.set(PREFERRED_LOCALE_COOKIE_NAME, value, { expires: 365, secure: document.location.protocol !== 'http:', diff --git a/content/README.md b/content/README.md index 43b1a87e60..af888602c4 100644 --- a/content/README.md +++ b/content/README.md @@ -228,7 +228,7 @@ defaultPlatform: linux ### `defaultTool` - Purpose: Override the initial tool selection for a page, where tool refers to the application the reader is using to work with GitHub (such as GitHub.com's web UI, the GitHub CLI, or GitHub Desktop) or the GitHub APIs (such as cURL or the GitHub CLI). For more information about the tool selector, see [Markup reference for GitHub Docs](../contributing/content-markup-reference.md#tool-tags). If this frontmatter is omitted, then the tool-specific content matching the GitHub web UI is shown by default. If a user has indicated a tool preference (by clicking on a tool tab), then the user's preference will be applied instead of the default value. -- Type: `String`, one of: `webui`, `cli`, `desktop`, `curl`, `codespaces`, `vscode`, `importer_cli`, `graphql`, `powershell`, `bash`. +- Type: `String`, one of: `webui`, `cli`, `desktop`, `curl`, `codespaces`, `vscode`, `importer_cli`, `graphql`, `powershell`, `bash`, `javascript`. - Optional. ```yaml diff --git a/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md index c5f72460c9..a4a0911750 100644 --- a/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md +++ b/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md @@ -27,7 +27,7 @@ You can configure environments with protection rules and secrets. When a workflo **Note:** You can only configure environments for public repositories. If you 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. -Organizations that use {% data variables.product.prodname_ghe_cloud %} can configure environments for private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment). {% data reusables.enterprise.link-to-ghec-trial %} +Organizations with {% data variables.product.prodname_team %} and users with {% data variables.product.prodname_pro %} can configure environments for private repositories. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)." {% endnote %} {% endif %} @@ -72,7 +72,7 @@ Secrets stored in an environment are only available to workflow jobs that refere {% ifversion fpt or ghec %} {% note %} -**Note:** To create an environment in a private repository, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} +**Note:** Creation of an environment in a private repository is available to organizations with {% data variables.product.prodname_team %} and users with {% data variables.product.prodname_pro %}. {% endnote %} {% endif %} diff --git a/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/content/actions/using-workflows/workflow-syntax-for-github-actions.md index 671f0dac0e..2607f856d8 100644 --- a/content/actions/using-workflows/workflow-syntax-for-github-actions.md +++ b/content/actions/using-workflows/workflow-syntax-for-github-actions.md @@ -538,6 +538,7 @@ You can override the default shell settings in the runner's operating system usi | Supported platform | `shell` parameter | Description | Command run internally | |--------------------|-------------------|-------------|------------------------| +| Linux / macOS | unspecified | The default shell on non-Windows platforms. Note that this runs a different command to when `bash` is specified explicitly. If `bash` is not found in the path, this is treated as `sh`. | `bash -e {0}` | | All | `bash` | The default shell on non-Windows platforms with a fallback to `sh`. When specifying a bash shell on Windows, the bash shell included with Git for Windows is used. | `bash --noprofile --norc -eo pipefail {0}` | | All | `pwsh` | The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `pwsh -command ". '{0}'"` | | All | `python` | Executes the python command. | `python {0}` | diff --git a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md index ed9eac86d7..2231f44590 100644 --- a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md +++ b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md @@ -97,7 +97,7 @@ Across all organizations owned by your enterprise, you can allow members to crea {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.repositories-tab %} 5. Under "Repository creation", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -{% ifversion ghes or ghae %} +{% ifversion ghes or ghae or ghec %} {% data reusables.enterprise-accounts.repo-creation-policy %} {% data reusables.enterprise-accounts.repo-creation-types %} {% else %} diff --git a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md index ec1e70ee35..e5ba3ebd96 100644 --- a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md +++ b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md @@ -32,7 +32,7 @@ The items in the table below can be migrated with a repository. Any items not sh |---------------------------------------------|--------| | Users | **@mentions** of users are rewritten to match the target. | Organizations | An organization's name and details are migrated. -| Repositories | Links to Git trees, blobs, commits, and lines are rewritten to match the target. The migrator follows a maximum of three repository redirects. +| Repositories | Links to Git trees, blobs, commits, and lines are rewritten to match the target. The migrator follows a maximum of three repository redirects. Internal repositories are migrated as private repositories. Archive status is unset. | Wikis | All wiki data is migrated. | Teams | **@mentions** of teams are rewritten to match the target. | Milestones | Timestamps are preserved. diff --git a/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md b/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md index 5c8b82b447..2ff593d9f8 100644 --- a/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md +++ b/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md @@ -41,13 +41,16 @@ After you authenticate to perform a sensitive action, your session is temporaril To confirm access for sudo mode, you {% ifversion totp-and-mobile-sudo-challenge %}can{% else %}must{% endif %} authenticate with your password.{% ifversion totp-and-mobile-sudo-challenge %} Optionally, you can use a different authentication method, like {% ifversion fpt or ghec %}a security key, {% data variables.product.prodname_mobile %}, or a 2FA code{% elsif ghes %}a security key or a 2FA code{% endif %}.{% endif %} -{% ifversion totp-and-mobile-sudo-challenge %} +{%- ifversion totp-and-mobile-sudo-challenge %} - [Confirming access using a security key](#confirming-access-using-a-security-key) {%- ifversion fpt or ghec %} - [Confirming access using GitHub Mobile](#confirming-access-using-github-mobile) {%- endif %} - [Confirming access using a 2FA code](#confirming-access-using-a-2fa-code) - [Confirming access using your password](#confirming-access-using-your-password) +{%- endif %} + +{% ifversion totp-and-mobile-sudo-challenge %} ### Confirming access using a security key @@ -57,8 +60,6 @@ When prompted to authenticate for sudo mode, click **Use security key**, then fo ![Screenshot of security key option for sudo mode](/assets/images/help/settings/sudo_mode_prompt_security_key.png) -{% endif %} - {% ifversion fpt or ghec %} ### Confirming access using {% data variables.product.prodname_mobile %} @@ -75,8 +76,6 @@ You must install and sign into {% data variables.product.prodname_mobile %} to c {% endif %} -{% ifversion totp-and-mobile-sudo-challenge %} - ### Confirming access using a 2FA code You must configure 2FA using a TOTP mobile app{% ifversion fpt or ghec %} or text messages{% endif %} to confirm access to your account for sudo mode using a 2FA code. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)." diff --git a/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md b/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md index cb14f04c2e..cf0d4da373 100644 --- a/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md +++ b/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md @@ -18,11 +18,26 @@ By default, your codespaces have access to all resources on the public internet, ## Connecting to resources on a private network -The currently supported method of accessing resources on a private network is to use a VPN. It is currently not recommended to allowlist codespaces IPs as this would allow all codespaces (both yours and those of other customers) access to the network protected resources. +There are currently two methods of accessing resources on a private network within Codespaces. +- Using a {% data variables.product.prodname_cli %} extension to configure your local machine as a gateway to remote resources. +- Using a VPN. + +### Using the GitHub CLI extension to access remote resources + +{% note %} + +**Note**: The {% data variables.product.prodname_cli %} extension is currently in beta and subject to change. + +{% endnote %} + +The {% data variables.product.prodname_cli %} extension allows you to create a bridge between a codespace and your local machine, so that the codespace can access any remote resource that is accessible from your machine. The codespace uses your local machine as a network gateway to reach those resources. For more information, see "[Using {% data variables.product.prodname_cli %} to access remote resources](https://github.com/github/gh-net#codespaces-network-bridge)." + + + ### Using a VPN to access resources behind a private network -The easiest way to access resources behind a private network is to VPN into that network from within your codespace. +As an alternative to the {% data variables.product.prodname_cli %} extension, you can use a VPN to access resources behind a private network from within your codespace. We recommend VPN tools like [OpenVPN](https://openvpn.net/) to access resources on a private network. For more information, see "[Using the OpenVPN client from GitHub Codespaces](https://github.com/codespaces-contrib/codespaces-openvpn)." diff --git a/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md b/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md index 35cb1858c5..37e405f2eb 100644 --- a/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md +++ b/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md @@ -30,6 +30,7 @@ You can work with {% data variables.product.prodname_codespaces %} in the {% da - [Copy a file to/from a codespace](#copy-a-file-tofrom-a-codespace) - [Modify ports in a codespace](#modify-ports-in-a-codespace) - [Access codespace logs](#access-codespace-logs) + - [Access remote resources](#access-remote-resources) ## Installing {% data variables.product.prodname_cli %} @@ -197,3 +198,12 @@ gh codespace logs -c codespace-name ``` For more information about the creation log, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs#creation-logs)." + +### Access remote resources +You can use the {% data variables.product.prodname_cli %} extension to create a bridge between a codespace and your local machine, so that the codespace can access any remote resource that is accessible from your machine. For more information on using the extension, see "[Using {% data variables.product.prodname_cli %} to access remote resources](https://github.com/github/gh-net#codespaces-network-bridge)." + +{% note %} + +**Note**: The {% data variables.product.prodname_cli %} extension is currently in beta and subject to change. + +{% endnote %} \ No newline at end of file diff --git a/content/communities/documenting-your-project-with-wikis/about-wikis.md b/content/communities/documenting-your-project-with-wikis/about-wikis.md index c9ab964dbd..d270e7ba51 100644 --- a/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -17,7 +17,9 @@ topics: Every repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} comes equipped with a section for hosting documentation, called a wiki. You can use your repository's wiki to share long-form content about your project, such as how to use it, how you designed it, or its core principles. A README file quickly tells what your project can do, while you can use a wiki to provide additional documentation. For more information, see "[About READMEs](/articles/about-readmes)." -With wikis, you can write content just like everywhere else on {% data variables.product.product_name %}. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)." We use [our open-source Markup library](https://github.com/github/markup) to convert different formats into HTML, so you can choose to write in Markdown or any other supported format. +With wikis, you can write content just like everywhere else on {% data variables.product.product_name %}. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)." We use [our open-source Markup library](https://github.com/github/markup) to convert different formats into HTML, so you can choose to write in Markdown or any other supported format. + +{% data reusables.getting-started.math-and-diagrams %} {% ifversion fpt or ghes or ghec %}If you create a wiki in a public repository, the wiki is available to {% ifversion ghes %}anyone with access to {% data variables.product.product_location %}{% else %}the public{% endif %}. {% endif %}If you create a wiki in a private{% ifversion ghec or ghes %} or internal{% endif %} repository, only {% ifversion fpt or ghes or ghec %}people{% elsif ghae %}enterprise members{% endif %} with access to the repository can access the wiki. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)." diff --git a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md index 95fb65a300..32dcbdc4b5 100644 --- a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md +++ b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md @@ -46,6 +46,11 @@ You can link to an image in a repository on {% data variables.product.product_na [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]] +{% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7647 %} +## Adding mathematical expressions and diagrams{% endif %} + +{% data reusables.getting-started.math-and-diagrams %} + ## Supported MediaWiki formats No matter which markup language your wiki page is written in, certain MediaWiki syntax will always be available to you. diff --git a/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index d6eaa28728..d3c60ccc0e 100644 --- a/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -1190,9 +1190,9 @@ Key | Type | Description `commits[][author][email]`|`string` | The git author's email address. `commits[][url]`|`url` | URL that points to the commit API resource. `commits[][distinct]`|`boolean` | Whether this commit is distinct from any that have been pushed before. -`commits[][added]`|`array` | An array of files added in the commit. -`commits[][modified]`|`array` | An array of files modified by the commit. -`commits[][removed]`|`array` | An array of files removed in the commit. +`commits[][added]`|`array` | An array of files added in the commit. For extremely large commits where {% data variables.product.product_name %} is unable to calculate this list in a timely manner, this may be empty even if files were added. +`commits[][modified]`|`array` | An array of files modified by the commit. For extremely large commits where {% data variables.product.product_name %} is unable to calculate this list in a timely manner, this may be empty even if files were modified. +`commits[][removed]`|`array` | An array of files removed in the commit. For extremely large commits where {% data variables.product.product_name %} is unable to calculate this list in a timely manner, this may be empty even if files were removed. `pusher` | `object` | The user who pushed the commits. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md index 8d0b98c315..4b690277a2 100644 --- a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md @@ -8,7 +8,7 @@ shortTitle: Create diagrams ## About creating diagrams -You can create diagrams in Markdown using three different syntaxes: mermaid, geoJSON and topoJSON, and ASCII STL. +You can create diagrams in Markdown using three different syntaxes: mermaid, geoJSON and topoJSON, and ASCII STL. Diagram rendering is available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, wikis, and Markdown files. ## Creating Mermaid diagrams diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md index 443ac80528..94b2e2bec0 100644 --- a/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md @@ -6,10 +6,14 @@ versions: shortTitle: Mathematical expressions --- +## About writing mathematical expressions + To enable clear communication of mathematical expressions, {% data variables.product.product_name %} supports LaTeX formatted math within Markdown. For more information, see [LaTeX/Mathematics](http://en.wikibooks.org/wiki/LaTeX/Mathematics) in Wikibooks. {% data variables.product.company_short %}'s math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide). +Mathematical expressions rendering is available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, {% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7647 %}wikis, {% endif %}and Markdown files. + ## Writing inline expressions To include a math expression inline with your text, delimit the expression with a dollar symbol `$`. diff --git a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md index 6c0cb23014..5b5dac7385 100644 --- a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md +++ b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md @@ -18,6 +18,8 @@ Verifying your domain stops other GitHub users from taking over your custom doma When you verify a domain, any immediate subdomains are also included in the verification. For example, if the `github.com` custom domain is verified, `docs.github.com`, `support.github.com`, and any other immediate subdomains will also be protected from takeovers. +{% data reusables.pages.wildcard-dns-warning %} + It's also possible to verify a domain for your organization{% ifversion ghec %} or enterprise{% endif %}, which displays a "Verified" badge on the organization {% ifversion ghec %}or enterprise{% endif %} profile{% ifversion ghec %} and, on {% data variables.product.prodname_ghe_cloud %}, allows you to restrict notifications to email addresses using the verified domain{% endif %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization){% ifversion ghec %}" and "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% endif %}." ## Verifying a domain for your user site @@ -28,7 +30,7 @@ It's also possible to verify a domain for your organization{% ifversion ghec %} 1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `USERNAME` with your username and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output. ``` dig _github-pages-challenge-USERNAME.example.com +nostats +nocomments +nocmd TXT - ``` + ``` {% data reusables.pages.settings-verify-domain-confirm %} ## Verifying a domain for your organization site @@ -42,5 +44,5 @@ Organization owners can verify custom domains for their organization. 1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `ORGANIZATION` with the name of your organization and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output. ``` dig _github-pages-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT - ``` + ``` {% data reusables.pages.settings-verify-domain-confirm %} diff --git a/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md index bf76deca2f..66158678f6 100644 --- a/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md +++ b/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -49,17 +49,11 @@ shortTitle: Configure publishing source If you choose the `docs` folder on any branch as your publishing source, then later remove the `/docs` folder from that branch in your repository, your site won't build and you'll get a page build error message for a missing `/docs` folder. For more information, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)." -{% ifversion fpt %} +{% ifversion build-pages-with-actions %} Your {% data variables.product.prodname_pages %} site will always be deployed with a {% data variables.product.prodname_actions %} workflow run, even if you've configured your {% data variables.product.prodname_pages %} site to be built using a different CI tool. Most external CI workflows "deploy" to GitHub Pages by committing the build output to the `gh-pages` branch of the repository, and typically include a `.nojekyll` file. When this happens, the {% data variables.product.prodname_actions %} workflow will detect the state that the branch does not need a build step, and will execute only the steps necessary to deploy the site to {% data variables.product.prodname_pages %} servers. -To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." - -{% note %} - -{% data reusables.pages.pages-builds-with-github-actions-public-beta %} - -{% endnote %} +To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." {% endif %} diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md index b76538436f..9e84172aa2 100644 --- a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md +++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -30,26 +30,27 @@ shortTitle: Jekyll build errors for Pages {% endnote %} +{% ifversion build-pages-with-actions %} +If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. +{% else %} If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. There are two main types of Jekyll build error messages. - A "Page build warning" message means your build completed successfully, but you may need to make changes to prevent future problems. - A "Page build failed" message means your build failed to complete. If Jekyll is able to detect a reason for the failure, you'll see a descriptive error message. +{% endif %} For more information about troubleshooting build errors, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)." -{% ifversion fpt %} +{% ifversion build-pages-with-actions %} ## Viewing Jekyll build error messages with {% data variables.product.prodname_actions %} By default, your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. To find potential build errors, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." -{% note %} - -{% data reusables.pages.pages-builds-with-github-actions-public-beta %} - -{% endnote %} {% endif %} +{% ifversion build-pages-with-actions %}{% else %} ## Viewing your repository's build failures on {% data variables.product.product_name %} You can see build failures (but not build warnings) for your site on {% data variables.product.product_name %} in the **Settings** tab of your site's repository. +{% endif %} ## Viewing Jekyll build error messages locally @@ -63,7 +64,7 @@ We recommend testing your site locally, which allows you to see build error mess ## Viewing Jekyll build errors by email -{% ifversion pages-custom-workflow %}If you are publishing from a branch, when{% else %}When{% endif %} you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. You'll also receive emails for build warnings. {% data reusables.pages.build-failure-email-server %} +{% ifversion pages-custom-workflow %}If you are publishing from a branch, when{% else %}When{% endif %} you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. {% data reusables.pages.build-failure-email-server %} {% ifversion pages-custom-workflow %}If you are publishing with a custom {% data variables.product.prodname_actions %} workflow, in order to receive emails about build errors in your pull request, you must configure your workflow to run on the `pull_request` trigger. When you do this, we recommend that you skip any deploy steps if the workflow was triggered by the `pull_request` event. This will allow you to see any build errors without deploying the changes from your pull request to your site. For more information, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows#pull_request)" and "[Expressions](/actions/learn-github-actions/expressions)."{% endif %} diff --git a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md index 2f9edbd00a..b1b70872ec 100644 --- a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md +++ b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md @@ -23,11 +23,18 @@ permissions: People with write access for a forked repository can sync the fork ## Syncing a fork branch from the web UI +{% ifversion syncing-fork-web-ui %} 1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. -2. Select the **Fetch upstream** drop-down. +2. Select the **Sync fork** dropdown. + !["Sync fork" dropdown emphasized](/assets/images/help/repository/sync-fork-dropdown.png) +3. Review the details about the commits from the upstream repository, then click **Update branch**. + ![Sync fork modal with "Update branch" button emphasized](/assets/images/help/repository/update-branch-button.png) +{% else %} +1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. +2. Select the **Fetch upstream** dropdown. !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png) 3. Review the details about the commits from the upstream repository, then click **Fetch and merge**. - !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png) + !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts. diff --git a/contributing/content-markup-reference.md b/contributing/content-markup-reference.md index 073c393321..c6408fe9b4 100644 --- a/contributing/content-markup-reference.md +++ b/contributing/content-markup-reference.md @@ -212,6 +212,14 @@ These instructions are pertinent to Bash shell commands. {% endbash %} ``` +``` +{% javascript %} + +These instructions are pertinent to javascript users. + +{% endjavascript %} +``` + You can define a default tool in the frontmatter. For more information, see the [content README](../content/README.md#defaulttool). ## Reusable and variable strings of text diff --git a/contributing/liquid-helpers.md b/contributing/liquid-helpers.md index 50027e96f0..5c96a1b490 100644 --- a/contributing/liquid-helpers.md +++ b/contributing/liquid-helpers.md @@ -42,8 +42,7 @@ If you define multiple products in the `versions` key within a page's YAML front Important notes: -* Use `ifversion` for product-based versioning. If you use `if` for product-based versioning, a test will fail. -* Use `if` for [feature-based versioning](#feature-based-versioning). +* Use `ifversion` for product-based versioning and [feature-based versioning](#feature-based-versioning). * Make sure to use `elsif` and not `else if`. Liquid does not recognize `else if` and will not render content inside an `else if` block. ### Comparison operators diff --git a/data/features/build-pages-with-actions.yml b/data/features/build-pages-with-actions.yml new file mode 100644 index 0000000000..458017e24d --- /dev/null +++ b/data/features/build-pages-with-actions.yml @@ -0,0 +1,5 @@ +# Issue 7584 +# Building Pages sites with Actions [GA] +versions: + fpt: '*' + ghec: '*' diff --git a/data/features/syncing-fork-web-ui.yml b/data/features/syncing-fork-web-ui.yml new file mode 100644 index 0000000000..05f39707de --- /dev/null +++ b/data/features/syncing-fork-web-ui.yml @@ -0,0 +1,7 @@ +# Issue 7629 +# Improved UI for manually syncing a fork +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.7' + ghae: 'issue-7629' diff --git a/data/features/totp-and-mobile-sudo-challenge.yml b/data/features/totp-and-mobile-sudo-challenge.yml index caf7524585..855e1b7203 100644 --- a/data/features/totp-and-mobile-sudo-challenge.yml +++ b/data/features/totp-and-mobile-sudo-challenge.yml @@ -1,6 +1,6 @@ # TOTP and mobile challenge for sudo mode prompt. versions: - fpt: '*' - ghec: '*' + #fpt: '*' + #ghec: '*' ghes: '>= 3.7' diff --git a/data/reusables/gated-features/environments.md b/data/reusables/gated-features/environments.md index a74a249da7..87a40b9ed1 100644 --- a/data/reusables/gated-features/environments.md +++ b/data/reusables/gated-features/environments.md @@ -1 +1 @@ -Environments, environment protection rules, and environment secrets are available in **public** repositories for all products. For access to environments in **private** repositories, you must use {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info %} +Environments, environment protection rules, and environment secrets are available in **public** repositories for all products. For access to environments in **private** or **internal** repositories, you must use {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info %} diff --git a/data/reusables/getting-started/math-and-diagrams.md b/data/reusables/getting-started/math-and-diagrams.md new file mode 100644 index 0000000000..0b8fd102b4 --- /dev/null +++ b/data/reusables/getting-started/math-and-diagrams.md @@ -0,0 +1 @@ +{% ifversion mermaid %}You can use Markdown to add rendered math expressions, diagrams, maps, and 3D models to your wiki. For more information on creating rendered math expressions, see "[Writing mathematical expressions](/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions)." For more information on creating diagrams, maps and 3D models, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)."{% endif %} \ No newline at end of file diff --git a/data/reusables/pages/check-workflow-run.md b/data/reusables/pages/check-workflow-run.md index f4f66b6f9f..1af0012c40 100644 --- a/data/reusables/pages/check-workflow-run.md +++ b/data/reusables/pages/check-workflow-run.md @@ -1,8 +1,10 @@ -{% ifversion fpt %} -1. Unless your {% data variables.product.prodname_pages %} site is built from a private or internal repository and published from a branch, your site is built and deployed with a {% data variables.product.prodname_actions %} workflow. For more information about how to view the workflow status, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." +{% ifversion build-pages-with-actions %} +1. Your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". -{% note %} + {% note %} -{% data reusables.pages.pages-builds-with-github-actions-public-beta %} + **Note:** {% data variables.product.prodname_actions %} is free for public repositories. Usage charges apply for private and internal repositories that go beyond the monthly allotment of free minutes. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration)". -{% endnote %}{% endif %} + {% endnote %} + +{% endif %} \ No newline at end of file diff --git a/data/reusables/pages/pages-builds-with-github-actions-public-beta.md b/data/reusables/pages/pages-builds-with-github-actions-public-beta.md deleted file mode 100644 index 0daefdc979..0000000000 --- a/data/reusables/pages/pages-builds-with-github-actions-public-beta.md +++ /dev/null @@ -1,5 +0,0 @@ -{% ifversion fpt %} - -**Note:** {% data variables.product.prodname_actions %} workflow runs for your {% data variables.product.prodname_pages %} sites are in public beta for public repositories and subject to change. {% data variables.product.prodname_actions %} workflow runs are free for public repositories. - -{% endif %} diff --git a/data/reusables/pages/wildcard-dns-warning.md b/data/reusables/pages/wildcard-dns-warning.md index 468c509c00..700c2473be 100644 --- a/data/reusables/pages/wildcard-dns-warning.md +++ b/data/reusables/pages/wildcard-dns-warning.md @@ -1,5 +1,5 @@ {% warning %} -**Warning:** We strongly recommend not using wildcard DNS records, such as `*.example.com`. A wildcard DNS record will allow anyone to host a {% data variables.product.prodname_pages %} site at one of your subdomains. +**Warning:** We strongly recommend not using wildcard DNS records, such as `*.example.com`. A wildcard DNS record will allow anyone to host a {% data variables.product.prodname_pages %} site at one of your subdomains even when they are verified. For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)." {% endwarning %} diff --git a/data/reusables/secret-scanning/secret-list-private-push-protection.md b/data/reusables/secret-scanning/secret-list-private-push-protection.md index fd323a2dd4..adc0cef6d8 100644 --- a/data/reusables/secret-scanning/secret-list-private-push-protection.md +++ b/data/reusables/secret-scanning/secret-list-private-push-protection.md @@ -10,6 +10,8 @@ Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_a Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token +{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %} +Azure | Azure Storage Account Key | azure_storage_account_key{% endif %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key Clojars | Clojars Deploy Token | clojars_deploy_token Databricks | Databricks Access Token | databricks_access_token diff --git a/data/ui.yml b/data/ui.yml index 485280fc40..693b3dcb09 100644 --- a/data/ui.yml +++ b/data/ui.yml @@ -14,11 +14,6 @@ header: English documentation. If there's a problem with translations on this page, please let us know. - localization_in_progress: - Hello, explorer! This page is under active development or - still in translation. For the most up-to-date and accurate information, - please visit our - English documentation. early_access: 📣 Please do not share this URL publicly. This page contains content about an early access feature. release_notes_use_latest: Please use the latest release for the latest security, performance, and bug fixes. # GHES release notes diff --git a/lib/all-tools.js b/lib/all-tools.js index 7ac1af7de0..92ae2dc597 100644 --- a/lib/all-tools.js +++ b/lib/all-tools.js @@ -10,4 +10,5 @@ export const allTools = { powershell: 'PowerShell', vscode: 'Visual Studio Code', webui: 'Web browser', + javascript: 'JavaScript', } diff --git a/lib/constants.js b/lib/constants.js new file mode 100644 index 0000000000..1c4e6fed62 --- /dev/null +++ b/lib/constants.js @@ -0,0 +1 @@ +export const PREFERRED_LOCALE_COOKIE_NAME = 'preferredlang' diff --git a/lib/redirects/static/client-side-rest-api-redirects.json b/lib/redirects/static/client-side-rest-api-redirects.json index 1ebad32cfe..1622d1017e 100644 --- a/lib/redirects/static/client-side-rest-api-redirects.json +++ b/lib/redirects/static/client-side-rest-api-redirects.json @@ -731,7 +731,7 @@ "/rest/pulls#list-pull-requests-files": "/rest/pulls/pulls#list-pull-requests-files", "/rest/pulls#check-if-a-pull-request-has-been-merged": "/rest/pulls/pulls#check-if-a-pull-request-has-been-merged", "/rest/pulls#merge-a-pull-request": "/rest/pulls/pulls#merge-a-pull-request", - "/rest/pulls#list-requested-reviewers-for-a-pull-request": "/rest/pulls/review-requests#list-requested-reviewers-for-a-pull-request", + "/rest/pulls#get-all-requested-reviewers-for-a-pull-request": "/rest/pulls/review-requests#get-all-requested-reviewers-for-a-pull-request", "/rest/pulls#review-requests": "/rest/pulls/review-requests", "/rest/pulls#request-reviewers-for-a-pull-request": "/rest/pulls/review-requests#request-reviewers-for-a-pull-request", "/rest/pulls#remove-requested-reviewers-from-a-pull-request": "/rest/pulls/review-requests#remove-requested-reviewers-from-a-pull-request", diff --git a/lib/rest/static/apps/enabled-for-apps.json b/lib/rest/static/apps/enabled-for-apps.json index 07a803e49f..476ae7a53c 100644 --- a/lib/rest/static/apps/enabled-for-apps.json +++ b/lib/rest/static/apps/enabled-for-apps.json @@ -2726,7 +2726,7 @@ "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/merge" }, { - "slug": "list-requested-reviewers-for-a-pull-request", + "slug": "get-all-requested-reviewers-for-a-pull-request", "subcategory": "review-requests", "verb": "get", "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers" @@ -5948,7 +5948,7 @@ "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/merge" }, { - "slug": "list-requested-reviewers-for-a-pull-request", + "slug": "get-all-requested-reviewers-for-a-pull-request", "subcategory": "review-requests", "verb": "get", "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers" @@ -9030,7 +9030,7 @@ "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/merge" }, { - "slug": "list-requested-reviewers-for-a-pull-request", + "slug": "get-all-requested-reviewers-for-a-pull-request", "subcategory": "review-requests", "verb": "get", "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers" @@ -12309,7 +12309,7 @@ "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/merge" }, { - "slug": "list-requested-reviewers-for-a-pull-request", + "slug": "get-all-requested-reviewers-for-a-pull-request", "subcategory": "review-requests", "verb": "get", "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers" @@ -15702,7 +15702,7 @@ "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/merge" }, { - "slug": "list-requested-reviewers-for-a-pull-request", + "slug": "get-all-requested-reviewers-for-a-pull-request", "subcategory": "review-requests", "verb": "get", "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers" @@ -19138,7 +19138,7 @@ "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/merge" }, { - "slug": "list-requested-reviewers-for-a-pull-request", + "slug": "get-all-requested-reviewers-for-a-pull-request", "subcategory": "review-requests", "verb": "get", "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers" @@ -22148,7 +22148,7 @@ "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/merge" }, { - "slug": "list-requested-reviewers-for-a-pull-request", + "slug": "get-all-requested-reviewers-for-a-pull-request", "subcategory": "review-requests", "verb": "get", "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers" diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json index e2908a32de..f9556142ae 100644 --- a/lib/rest/static/decorated/api.github.com.json +++ b/lib/rest/static/decorated/api.github.com.json @@ -29808,7 +29808,7 @@ }, { "name": "status", - "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested. For a list of the possible status and conclusion options, see \"Create a check run.\"

", + "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested.

", "in": "query", "required": false, "schema": { @@ -48408,7 +48408,7 @@ }, { "name": "status", - "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested. For a list of the possible status and conclusion options, see \"Create a check run.\"

", + "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested.

", "in": "query", "required": false, "schema": { @@ -90390,15 +90390,6 @@ "format": "date-time" } }, - { - "name": "per_page", - "description": "

The number of results per page (max 100).

", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, { "name": "page", "description": "

Page number of the results to fetch.

", @@ -90407,6 +90398,15 @@ "type": "integer", "default": 1 } + }, + { + "name": "per_page", + "description": "

The number of results per page (max 50).

", + "in": "query", + "schema": { + "type": "integer", + "default": 50 + } } ], "bodyParameters": [], @@ -114058,7 +114058,7 @@ "description": "Example", "acceptHeader": "application/vnd.github.v3+json", "bodyParameters": { - "respoitory": "Hello-World", + "repository": "Hello-World", "permissions": { "issues": "write", "contents": "read" @@ -287993,9 +287993,10 @@ }, { "name": "ref", - "description": "

ref parameter

", + "description": "

The name of the fully qualified reference to update. For example, refs/heads/master. If the value doesn't start with refs and have at least two slashes, it will be rejected.

", "in": "path", "required": true, + "example": "refs/head/master", "schema": { "type": "string" }, @@ -289089,7 +289090,7 @@ } ], "previews": [], - "descriptionHTML": "

The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.

\n

If you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"Create a commit\" and \"Update a reference.\"

", + "descriptionHTML": "

The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.

\n

If you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"Create a commit\" and \"Update a reference.\"

\n

Returns an error if you try to delete a file that does not exist.

", "statusCodes": [ { "httpStatusCode": "201", @@ -429372,11 +429373,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The title of the new pull request.

", + "description": "

The title of the new pull request. Required unless issue is specified.

", "name": "title", "in": "body", "rawType": "string", - "rawDescription": "The title of the new pull request.", + "rawDescription": "The title of the new pull request. Required unless `issue` is specified.", "isRequired": false, "childParamsGroups": [] }, @@ -429432,13 +429433,14 @@ }, { "type": "integer", + "description": "

An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless title is specified.

", "examples": [ 1 ], "name": "issue", "in": "body", "rawType": "integer", - "description": "", + "rawDescription": "An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless `title` is specified.", "isRequired": false, "childParamsGroups": [] } @@ -433207,7 +433209,7 @@ } ], "previews": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "statusCodes": [ { "httpStatusCode": "201", @@ -445018,7 +445020,7 @@ "in": "body", "rawType": "string", "rawDescription": "The SHA of the commit needing a comment. Not using the latest commit SHA may render your comment outdated if a subsequent commit modifies the line you specify as the `position`.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -445028,7 +445030,7 @@ "in": "body", "rawType": "string", "rawDescription": "The relative path to the file that necessitates a comment.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -445066,7 +445068,7 @@ "in": "body", "rawType": "integer", "rawDescription": "The line of the blob in the pull request diff that the comment applies to. For a multi-line comment, the last line of the range that your comment applies to.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -446358,7 +446360,7 @@ "serverUrl": "https://api.github.com", "verb": "get", "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers", - "title": "List requested reviewers for a pull request", + "title": "Get all requested reviewers for a pull request", "category": "pulls", "subcategory": "review-requests", "parameters": [ @@ -446388,24 +446390,6 @@ "schema": { "type": "integer" } - }, - { - "name": "per_page", - "description": "

The number of results per page (max 100).

", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, - { - "name": "page", - "description": "

Page number of the results to fetch.

", - "in": "query", - "schema": { - "type": "integer", - "default": 1 - } } ], "bodyParameters": [], @@ -446848,7 +446832,7 @@ } ], "previews": [], - "descriptionHTML": "

Lists the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the List reviews for a pull request operation.

", + "descriptionHTML": "

Gets the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the List reviews for a pull request operation.

", "statusCodes": [ { "httpStatusCode": "200", @@ -461809,7 +461793,7 @@ } ], "previews": [], - "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", + "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", "statusCodes": [ { "httpStatusCode": "200", diff --git a/lib/rest/static/decorated/ghes-3.2.json b/lib/rest/static/decorated/ghes-3.2.json index 3360e2f711..04dbd3702a 100644 --- a/lib/rest/static/decorated/ghes-3.2.json +++ b/lib/rest/static/decorated/ghes-3.2.json @@ -24609,7 +24609,7 @@ }, { "name": "status", - "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested. For a list of the possible status and conclusion options, see \"Create a check run.\"

", + "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested.

", "in": "query", "required": false, "schema": { @@ -36436,7 +36436,7 @@ }, { "name": "status", - "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested. For a list of the possible status and conclusion options, see \"Create a check run.\"

", + "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested.

", "in": "query", "required": false, "schema": { @@ -77641,15 +77641,6 @@ "format": "date-time" } }, - { - "name": "per_page", - "description": "

The number of results per page (max 100).

", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, { "name": "page", "description": "

Page number of the results to fetch.

", @@ -77658,6 +77649,15 @@ "type": "integer", "default": 1 } + }, + { + "name": "per_page", + "description": "

The number of results per page (max 50).

", + "in": "query", + "schema": { + "type": "integer", + "default": 50 + } } ], "bodyParameters": [], @@ -101148,7 +101148,7 @@ "description": "Example", "acceptHeader": "application/vnd.github.v3+json", "bodyParameters": { - "respoitory": "Hello-World", + "repository": "Hello-World", "permissions": { "issues": "write", "contents": "read" @@ -186889,19 +186889,7 @@ "statusCode": "200", "contentType": "application/json", "description": "

Response

", - "example": [ - { - "id": 1, - "key": "ssh-rsa AAA...", - "url": "https://api.github.com/repos/octocat/Hello-World/keys/1", - "title": "octocat@octomac", - "verified": true, - "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" - } - ], + "example": {}, "schema": { "type": "array", "items": { @@ -186929,18 +186917,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -187054,9 +187030,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true }, "schema": { "title": "Deploy Key", @@ -187083,18 +187057,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -187184,9 +187146,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true }, "schema": { "title": "Deploy Key", @@ -187213,18 +187173,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -203170,19 +203118,6 @@ "created_at": { "type": "string", "format": "date-time" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ], - "format": "date-time" } }, "required": [ @@ -219300,9 +219235,10 @@ }, { "name": "ref", - "description": "

ref parameter

", + "description": "

The name of the fully qualified reference to update. For example, refs/heads/master. If the value doesn't start with refs and have at least two slashes, it will be rejected.

", "in": "path", "required": true, + "example": "refs/head/master", "schema": { "type": "string" }, @@ -220396,7 +220332,7 @@ } ], "previews": [], - "descriptionHTML": "

The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.

\n

If you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"Create a commit\" and \"Update a reference.\"

", + "descriptionHTML": "

The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.

\n

If you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"Create a commit\" and \"Update a reference.\"

\n

Returns an error if you try to delete a file that does not exist.

", "statusCodes": [ { "httpStatusCode": "201", @@ -326719,11 +326655,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The title of the new pull request.

", + "description": "

The title of the new pull request. Required unless issue is specified.

", "name": "title", "in": "body", "rawType": "string", - "rawDescription": "The title of the new pull request.", + "rawDescription": "The title of the new pull request. Required unless `issue` is specified.", "isRequired": false, "childParamsGroups": [] }, @@ -326779,13 +326715,14 @@ }, { "type": "integer", + "description": "

An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless title is specified.

", "examples": [ 1 ], "name": "issue", "in": "body", "rawType": "integer", - "description": "", + "rawDescription": "An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless `title` is specified.", "isRequired": false, "childParamsGroups": [] } @@ -330554,7 +330491,7 @@ } ], "previews": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "statusCodes": [ { "httpStatusCode": "201", @@ -342378,7 +342315,7 @@ "in": "body", "rawType": "string", "rawDescription": "The SHA of the commit needing a comment. Not using the latest commit SHA may render your comment outdated if a subsequent commit modifies the line you specify as the `position`.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -342388,7 +342325,7 @@ "in": "body", "rawType": "string", "rawDescription": "The relative path to the file that necessitates a comment.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -342426,7 +342363,7 @@ "in": "body", "rawType": "integer", "rawDescription": "**Required with `comfort-fade` preview**. The line of the blob in the pull request diff that the comment applies to. For a multi-line comment, the last line of the range that your comment applies to.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -343720,7 +343657,7 @@ "serverUrl": "http(s)://HOSTNAME/api/v3", "verb": "get", "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers", - "title": "List requested reviewers for a pull request", + "title": "Get all requested reviewers for a pull request", "category": "pulls", "subcategory": "review-requests", "parameters": [ @@ -343750,24 +343687,6 @@ "schema": { "type": "integer" } - }, - { - "name": "per_page", - "description": "

The number of results per page (max 100).

", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, - { - "name": "page", - "description": "

Page number of the results to fetch.

", - "in": "query", - "schema": { - "type": "integer", - "default": 1 - } } ], "bodyParameters": [], @@ -344210,7 +344129,7 @@ } ], "previews": [], - "descriptionHTML": "

Lists the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the List reviews for a pull request operation.

", + "descriptionHTML": "

Gets the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the List reviews for a pull request operation.

", "statusCodes": [ { "httpStatusCode": "200", @@ -359095,7 +359014,7 @@ } ], "previews": [], - "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", + "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", "statusCodes": [ { "httpStatusCode": "200", diff --git a/lib/rest/static/decorated/ghes-3.3.json b/lib/rest/static/decorated/ghes-3.3.json index b8cff72547..92b3f43eca 100644 --- a/lib/rest/static/decorated/ghes-3.3.json +++ b/lib/rest/static/decorated/ghes-3.3.json @@ -24845,7 +24845,7 @@ }, { "name": "status", - "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested. For a list of the possible status and conclusion options, see \"Create a check run.\"

", + "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested.

", "in": "query", "required": false, "schema": { @@ -36716,7 +36716,7 @@ }, { "name": "status", - "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested. For a list of the possible status and conclusion options, see \"Create a check run.\"

", + "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested.

", "in": "query", "required": false, "schema": { @@ -78042,15 +78042,6 @@ "format": "date-time" } }, - { - "name": "per_page", - "description": "

The number of results per page (max 100).

", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, { "name": "page", "description": "

Page number of the results to fetch.

", @@ -78059,6 +78050,15 @@ "type": "integer", "default": 1 } + }, + { + "name": "per_page", + "description": "

The number of results per page (max 50).

", + "in": "query", + "schema": { + "type": "integer", + "default": 50 + } } ], "bodyParameters": [], @@ -101650,7 +101650,7 @@ "description": "Example", "acceptHeader": "application/vnd.github.v3+json", "bodyParameters": { - "respoitory": "Hello-World", + "repository": "Hello-World", "permissions": { "issues": "write", "contents": "read" @@ -187702,19 +187702,7 @@ "statusCode": "200", "contentType": "application/json", "description": "

Response

", - "example": [ - { - "id": 1, - "key": "ssh-rsa AAA...", - "url": "https://api.github.com/repos/octocat/Hello-World/keys/1", - "title": "octocat@octomac", - "verified": true, - "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" - } - ], + "example": {}, "schema": { "type": "array", "items": { @@ -187742,18 +187730,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -187867,9 +187843,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true }, "schema": { "title": "Deploy Key", @@ -187896,18 +187870,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -187997,9 +187959,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true }, "schema": { "title": "Deploy Key", @@ -188026,18 +187986,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -204282,19 +204230,6 @@ "created_at": { "type": "string", "format": "date-time" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ], - "format": "date-time" } }, "required": [ @@ -220412,9 +220347,10 @@ }, { "name": "ref", - "description": "

ref parameter

", + "description": "

The name of the fully qualified reference to update. For example, refs/heads/master. If the value doesn't start with refs and have at least two slashes, it will be rejected.

", "in": "path", "required": true, + "example": "refs/head/master", "schema": { "type": "string" }, @@ -221508,7 +221444,7 @@ } ], "previews": [], - "descriptionHTML": "

The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.

\n

If you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"Create a commit\" and \"Update a reference.\"

", + "descriptionHTML": "

The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.

\n

If you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"Create a commit\" and \"Update a reference.\"

\n

Returns an error if you try to delete a file that does not exist.

", "statusCodes": [ { "httpStatusCode": "201", @@ -328291,11 +328227,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The title of the new pull request.

", + "description": "

The title of the new pull request. Required unless issue is specified.

", "name": "title", "in": "body", "rawType": "string", - "rawDescription": "The title of the new pull request.", + "rawDescription": "The title of the new pull request. Required unless `issue` is specified.", "isRequired": false, "childParamsGroups": [] }, @@ -328351,13 +328287,14 @@ }, { "type": "integer", + "description": "

An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless title is specified.

", "examples": [ 1 ], "name": "issue", "in": "body", "rawType": "integer", - "description": "", + "rawDescription": "An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless `title` is specified.", "isRequired": false, "childParamsGroups": [] } @@ -332126,7 +332063,7 @@ } ], "previews": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "statusCodes": [ { "httpStatusCode": "201", @@ -343937,7 +343874,7 @@ "in": "body", "rawType": "string", "rawDescription": "The SHA of the commit needing a comment. Not using the latest commit SHA may render your comment outdated if a subsequent commit modifies the line you specify as the `position`.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -343947,7 +343884,7 @@ "in": "body", "rawType": "string", "rawDescription": "The relative path to the file that necessitates a comment.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -343985,7 +343922,7 @@ "in": "body", "rawType": "integer", "rawDescription": "The line of the blob in the pull request diff that the comment applies to. For a multi-line comment, the last line of the range that your comment applies to.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -345277,7 +345214,7 @@ "serverUrl": "http(s)://HOSTNAME/api/v3", "verb": "get", "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers", - "title": "List requested reviewers for a pull request", + "title": "Get all requested reviewers for a pull request", "category": "pulls", "subcategory": "review-requests", "parameters": [ @@ -345307,24 +345244,6 @@ "schema": { "type": "integer" } - }, - { - "name": "per_page", - "description": "

The number of results per page (max 100).

", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, - { - "name": "page", - "description": "

Page number of the results to fetch.

", - "in": "query", - "schema": { - "type": "integer", - "default": 1 - } } ], "bodyParameters": [], @@ -345767,7 +345686,7 @@ } ], "previews": [], - "descriptionHTML": "

Lists the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the List reviews for a pull request operation.

", + "descriptionHTML": "

Gets the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the List reviews for a pull request operation.

", "statusCodes": [ { "httpStatusCode": "200", @@ -360696,7 +360615,7 @@ } ], "previews": [], - "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", + "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", "statusCodes": [ { "httpStatusCode": "200", diff --git a/lib/rest/static/decorated/ghes-3.4.json b/lib/rest/static/decorated/ghes-3.4.json index a690133aa6..342577706e 100644 --- a/lib/rest/static/decorated/ghes-3.4.json +++ b/lib/rest/static/decorated/ghes-3.4.json @@ -26978,7 +26978,7 @@ }, { "name": "status", - "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested. For a list of the possible status and conclusion options, see \"Create a check run.\"

", + "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested.

", "in": "query", "required": false, "schema": { @@ -38849,7 +38849,7 @@ }, { "name": "status", - "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested. For a list of the possible status and conclusion options, see \"Create a check run.\"

", + "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested.

", "in": "query", "required": false, "schema": { @@ -80175,15 +80175,6 @@ "format": "date-time" } }, - { - "name": "per_page", - "description": "

The number of results per page (max 100).

", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, { "name": "page", "description": "

Page number of the results to fetch.

", @@ -80192,6 +80183,15 @@ "type": "integer", "default": 1 } + }, + { + "name": "per_page", + "description": "

The number of results per page (max 50).

", + "in": "query", + "schema": { + "type": "integer", + "default": 50 + } } ], "bodyParameters": [], @@ -103741,7 +103741,7 @@ "description": "Example", "acceptHeader": "application/vnd.github.v3+json", "bodyParameters": { - "respoitory": "Hello-World", + "repository": "Hello-World", "permissions": { "issues": "write", "contents": "read" @@ -195501,19 +195501,7 @@ "statusCode": "200", "contentType": "application/json", "description": "

Response

", - "example": [ - { - "id": 1, - "key": "ssh-rsa AAA...", - "url": "https://api.github.com/repos/octocat/Hello-World/keys/1", - "title": "octocat@octomac", - "verified": true, - "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" - } - ], + "example": {}, "schema": { "type": "array", "items": { @@ -195541,18 +195529,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -195666,9 +195642,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true }, "schema": { "title": "Deploy Key", @@ -195695,18 +195669,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -195796,9 +195758,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true }, "schema": { "title": "Deploy Key", @@ -195825,18 +195785,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -212261,19 +212209,6 @@ "created_at": { "type": "string", "format": "date-time" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ], - "format": "date-time" } }, "required": [ @@ -228367,9 +228302,10 @@ }, { "name": "ref", - "description": "

ref parameter

", + "description": "

The name of the fully qualified reference to update. For example, refs/heads/master. If the value doesn't start with refs and have at least two slashes, it will be rejected.

", "in": "path", "required": true, + "example": "refs/head/master", "schema": { "type": "string" }, @@ -229463,7 +229399,7 @@ } ], "previews": [], - "descriptionHTML": "

The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.

\n

If you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"Create a commit\" and \"Update a reference.\"

", + "descriptionHTML": "

The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.

\n

If you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"Create a commit\" and \"Update a reference.\"

\n

Returns an error if you try to delete a file that does not exist.

", "statusCodes": [ { "httpStatusCode": "201", @@ -348272,11 +348208,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The title of the new pull request.

", + "description": "

The title of the new pull request. Required unless issue is specified.

", "name": "title", "in": "body", "rawType": "string", - "rawDescription": "The title of the new pull request.", + "rawDescription": "The title of the new pull request. Required unless `issue` is specified.", "isRequired": false, "childParamsGroups": [] }, @@ -348332,13 +348268,14 @@ }, { "type": "integer", + "description": "

An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless title is specified.

", "examples": [ 1 ], "name": "issue", "in": "body", "rawType": "integer", - "description": "", + "rawDescription": "An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless `title` is specified.", "isRequired": false, "childParamsGroups": [] } @@ -352107,7 +352044,7 @@ } ], "previews": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "statusCodes": [ { "httpStatusCode": "201", @@ -363918,7 +363855,7 @@ "in": "body", "rawType": "string", "rawDescription": "The SHA of the commit needing a comment. Not using the latest commit SHA may render your comment outdated if a subsequent commit modifies the line you specify as the `position`.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -363928,7 +363865,7 @@ "in": "body", "rawType": "string", "rawDescription": "The relative path to the file that necessitates a comment.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -363966,7 +363903,7 @@ "in": "body", "rawType": "integer", "rawDescription": "The line of the blob in the pull request diff that the comment applies to. For a multi-line comment, the last line of the range that your comment applies to.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -365258,7 +365195,7 @@ "serverUrl": "http(s)://HOSTNAME/api/v3", "verb": "get", "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers", - "title": "List requested reviewers for a pull request", + "title": "Get all requested reviewers for a pull request", "category": "pulls", "subcategory": "review-requests", "parameters": [ @@ -365288,24 +365225,6 @@ "schema": { "type": "integer" } - }, - { - "name": "per_page", - "description": "

The number of results per page (max 100).

", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, - { - "name": "page", - "description": "

Page number of the results to fetch.

", - "in": "query", - "schema": { - "type": "integer", - "default": 1 - } } ], "bodyParameters": [], @@ -365748,7 +365667,7 @@ } ], "previews": [], - "descriptionHTML": "

Lists the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the List reviews for a pull request operation.

", + "descriptionHTML": "

Gets the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the List reviews for a pull request operation.

", "statusCodes": [ { "httpStatusCode": "200", @@ -380677,7 +380596,7 @@ } ], "previews": [], - "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", + "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", "statusCodes": [ { "httpStatusCode": "200", diff --git a/lib/rest/static/decorated/ghes-3.5.json b/lib/rest/static/decorated/ghes-3.5.json index 4c6d9d9ab5..f96804af9c 100644 --- a/lib/rest/static/decorated/ghes-3.5.json +++ b/lib/rest/static/decorated/ghes-3.5.json @@ -28844,7 +28844,7 @@ }, { "name": "status", - "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested. For a list of the possible status and conclusion options, see \"Create a check run.\"

", + "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested.

", "in": "query", "required": false, "schema": { @@ -46923,7 +46923,7 @@ }, { "name": "status", - "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested. For a list of the possible status and conclusion options, see \"Create a check run.\"

", + "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested.

", "in": "query", "required": false, "schema": { @@ -88655,15 +88655,6 @@ "format": "date-time" } }, - { - "name": "per_page", - "description": "

The number of results per page (max 100).

", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, { "name": "page", "description": "

Page number of the results to fetch.

", @@ -88672,6 +88663,15 @@ "type": "integer", "default": 1 } + }, + { + "name": "per_page", + "description": "

The number of results per page (max 50).

", + "in": "query", + "schema": { + "type": "integer", + "default": 50 + } } ], "bodyParameters": [], @@ -112251,7 +112251,7 @@ "description": "Example", "acceptHeader": "application/vnd.github.v3+json", "bodyParameters": { - "respoitory": "Hello-World", + "repository": "Hello-World", "permissions": { "issues": "write", "contents": "read" @@ -205492,19 +205492,7 @@ "statusCode": "200", "contentType": "application/json", "description": "

Response

", - "example": [ - { - "id": 1, - "key": "ssh-rsa AAA...", - "url": "https://api.github.com/repos/octocat/Hello-World/keys/1", - "title": "octocat@octomac", - "verified": true, - "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" - } - ], + "example": {}, "schema": { "type": "array", "items": { @@ -205532,18 +205520,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -205657,9 +205633,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true }, "schema": { "title": "Deploy Key", @@ -205686,18 +205660,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -205787,9 +205749,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true }, "schema": { "title": "Deploy Key", @@ -205816,18 +205776,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -222252,19 +222200,6 @@ "created_at": { "type": "string", "format": "date-time" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ], - "format": "date-time" } }, "required": [ @@ -238358,9 +238293,10 @@ }, { "name": "ref", - "description": "

ref parameter

", + "description": "

The name of the fully qualified reference to update. For example, refs/heads/master. If the value doesn't start with refs and have at least two slashes, it will be rejected.

", "in": "path", "required": true, + "example": "refs/head/master", "schema": { "type": "string" }, @@ -239454,7 +239390,7 @@ } ], "previews": [], - "descriptionHTML": "

The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.

\n

If you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"Create a commit\" and \"Update a reference.\"

", + "descriptionHTML": "

The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.

\n

If you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"Create a commit\" and \"Update a reference.\"

\n

Returns an error if you try to delete a file that does not exist.

", "statusCodes": [ { "httpStatusCode": "201", @@ -358269,11 +358205,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The title of the new pull request.

", + "description": "

The title of the new pull request. Required unless issue is specified.

", "name": "title", "in": "body", "rawType": "string", - "rawDescription": "The title of the new pull request.", + "rawDescription": "The title of the new pull request. Required unless `issue` is specified.", "isRequired": false, "childParamsGroups": [] }, @@ -358329,13 +358265,14 @@ }, { "type": "integer", + "description": "

An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless title is specified.

", "examples": [ 1 ], "name": "issue", "in": "body", "rawType": "integer", - "description": "", + "rawDescription": "An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless `title` is specified.", "isRequired": false, "childParamsGroups": [] } @@ -362104,7 +362041,7 @@ } ], "previews": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "statusCodes": [ { "httpStatusCode": "201", @@ -373915,7 +373852,7 @@ "in": "body", "rawType": "string", "rawDescription": "The SHA of the commit needing a comment. Not using the latest commit SHA may render your comment outdated if a subsequent commit modifies the line you specify as the `position`.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -373925,7 +373862,7 @@ "in": "body", "rawType": "string", "rawDescription": "The relative path to the file that necessitates a comment.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -373963,7 +373900,7 @@ "in": "body", "rawType": "integer", "rawDescription": "The line of the blob in the pull request diff that the comment applies to. For a multi-line comment, the last line of the range that your comment applies to.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -375255,7 +375192,7 @@ "serverUrl": "http(s)://HOSTNAME/api/v3", "verb": "get", "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers", - "title": "List requested reviewers for a pull request", + "title": "Get all requested reviewers for a pull request", "category": "pulls", "subcategory": "review-requests", "parameters": [ @@ -375285,24 +375222,6 @@ "schema": { "type": "integer" } - }, - { - "name": "per_page", - "description": "

The number of results per page (max 100).

", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, - { - "name": "page", - "description": "

Page number of the results to fetch.

", - "in": "query", - "schema": { - "type": "integer", - "default": 1 - } } ], "bodyParameters": [], @@ -375745,7 +375664,7 @@ } ], "previews": [], - "descriptionHTML": "

Lists the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the List reviews for a pull request operation.

", + "descriptionHTML": "

Gets the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the List reviews for a pull request operation.

", "statusCodes": [ { "httpStatusCode": "200", @@ -390674,7 +390593,7 @@ } ], "previews": [], - "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", + "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", "statusCodes": [ { "httpStatusCode": "200", diff --git a/lib/rest/static/decorated/ghes-3.6.json b/lib/rest/static/decorated/ghes-3.6.json index ab4cfa260a..e8a8622ca5 100644 --- a/lib/rest/static/decorated/ghes-3.6.json +++ b/lib/rest/static/decorated/ghes-3.6.json @@ -29297,7 +29297,7 @@ }, { "name": "status", - "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested. For a list of the possible status and conclusion options, see \"Create a check run.\"

", + "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested.

", "in": "query", "required": false, "schema": { @@ -47581,7 +47581,7 @@ }, { "name": "status", - "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested. For a list of the possible status and conclusion options, see \"Create a check run.\"

", + "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested.

", "in": "query", "required": false, "schema": { @@ -89434,15 +89434,6 @@ "format": "date-time" } }, - { - "name": "per_page", - "description": "

The number of results per page (max 100).

", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, { "name": "page", "description": "

Page number of the results to fetch.

", @@ -89451,6 +89442,15 @@ "type": "integer", "default": 1 } + }, + { + "name": "per_page", + "description": "

The number of results per page (max 50).

", + "in": "query", + "schema": { + "type": "integer", + "default": 50 + } } ], "bodyParameters": [], @@ -113102,7 +113102,7 @@ "description": "Example", "acceptHeader": "application/vnd.github.v3+json", "bodyParameters": { - "respoitory": "Hello-World", + "repository": "Hello-World", "permissions": { "issues": "write", "contents": "read" @@ -206770,19 +206770,7 @@ "statusCode": "200", "contentType": "application/json", "description": "

Response

", - "example": [ - { - "id": 1, - "key": "ssh-rsa AAA...", - "url": "https://api.github.com/repos/octocat/Hello-World/keys/1", - "title": "octocat@octomac", - "verified": true, - "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" - } - ], + "example": {}, "schema": { "type": "array", "items": { @@ -206810,18 +206798,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -206935,9 +206911,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true }, "schema": { "title": "Deploy Key", @@ -206964,18 +206938,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -207065,9 +207027,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true }, "schema": { "title": "Deploy Key", @@ -207094,18 +207054,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -223530,19 +223478,6 @@ "created_at": { "type": "string", "format": "date-time" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ], - "format": "date-time" } }, "required": [ @@ -239636,9 +239571,10 @@ }, { "name": "ref", - "description": "

ref parameter

", + "description": "

The name of the fully qualified reference to update. For example, refs/heads/master. If the value doesn't start with refs and have at least two slashes, it will be rejected.

", "in": "path", "required": true, + "example": "refs/head/master", "schema": { "type": "string" }, @@ -240732,7 +240668,7 @@ } ], "previews": [], - "descriptionHTML": "

The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.

\n

If you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"Create a commit\" and \"Update a reference.\"

", + "descriptionHTML": "

The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.

\n

If you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"Create a commit\" and \"Update a reference.\"

\n

Returns an error if you try to delete a file that does not exist.

", "statusCodes": [ { "httpStatusCode": "201", @@ -359707,11 +359643,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The title of the new pull request.

", + "description": "

The title of the new pull request. Required unless issue is specified.

", "name": "title", "in": "body", "rawType": "string", - "rawDescription": "The title of the new pull request.", + "rawDescription": "The title of the new pull request. Required unless `issue` is specified.", "isRequired": false, "childParamsGroups": [] }, @@ -359767,13 +359703,14 @@ }, { "type": "integer", + "description": "

An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless title is specified.

", "examples": [ 1 ], "name": "issue", "in": "body", "rawType": "integer", - "description": "", + "rawDescription": "An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless `title` is specified.", "isRequired": false, "childParamsGroups": [] } @@ -363542,7 +363479,7 @@ } ], "previews": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "statusCodes": [ { "httpStatusCode": "201", @@ -375353,7 +375290,7 @@ "in": "body", "rawType": "string", "rawDescription": "The SHA of the commit needing a comment. Not using the latest commit SHA may render your comment outdated if a subsequent commit modifies the line you specify as the `position`.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -375363,7 +375300,7 @@ "in": "body", "rawType": "string", "rawDescription": "The relative path to the file that necessitates a comment.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -375401,7 +375338,7 @@ "in": "body", "rawType": "integer", "rawDescription": "The line of the blob in the pull request diff that the comment applies to. For a multi-line comment, the last line of the range that your comment applies to.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -376693,7 +376630,7 @@ "serverUrl": "http(s)://HOSTNAME/api/v3", "verb": "get", "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers", - "title": "List requested reviewers for a pull request", + "title": "Get all requested reviewers for a pull request", "category": "pulls", "subcategory": "review-requests", "parameters": [ @@ -376723,24 +376660,6 @@ "schema": { "type": "integer" } - }, - { - "name": "per_page", - "description": "

The number of results per page (max 100).

", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, - { - "name": "page", - "description": "

Page number of the results to fetch.

", - "in": "query", - "schema": { - "type": "integer", - "default": 1 - } } ], "bodyParameters": [], @@ -377183,7 +377102,7 @@ } ], "previews": [], - "descriptionHTML": "

Lists the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the List reviews for a pull request operation.

", + "descriptionHTML": "

Gets the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the List reviews for a pull request operation.

", "statusCodes": [ { "httpStatusCode": "200", @@ -392144,7 +392063,7 @@ } ], "previews": [], - "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", + "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", "statusCodes": [ { "httpStatusCode": "200", diff --git a/lib/rest/static/decorated/github.ae.json b/lib/rest/static/decorated/github.ae.json index 0838a2aad2..f151dc9ae0 100644 --- a/lib/rest/static/decorated/github.ae.json +++ b/lib/rest/static/decorated/github.ae.json @@ -21410,7 +21410,7 @@ }, { "name": "status", - "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested. For a list of the possible status and conclusion options, see \"Create a check run.\"

", + "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested.

", "in": "query", "required": false, "schema": { @@ -38033,7 +38033,7 @@ }, { "name": "status", - "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested. For a list of the possible status and conclusion options, see \"Create a check run.\"

", + "description": "

Returns workflow runs with the check run status or conclusion that you specify. For example, a conclusion can be success or a status can be in_progress. Only GitHub can set a status of waiting or requested.

", "in": "query", "required": false, "schema": { @@ -56285,15 +56285,6 @@ "format": "date-time" } }, - { - "name": "per_page", - "description": "

The number of results per page (max 100).

", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, { "name": "page", "description": "

Page number of the results to fetch.

", @@ -56302,6 +56293,15 @@ "type": "integer", "default": 1 } + }, + { + "name": "per_page", + "description": "

The number of results per page (max 50).

", + "in": "query", + "schema": { + "type": "integer", + "default": 50 + } } ], "bodyParameters": [], @@ -79881,7 +79881,7 @@ "description": "Example", "acceptHeader": "application/vnd.github.v3+json", "bodyParameters": { - "respoitory": "Hello-World", + "repository": "Hello-World", "permissions": { "issues": "write", "contents": "read" @@ -164137,19 +164137,7 @@ "statusCode": "200", "contentType": "application/json", "description": "

Response

", - "example": [ - { - "id": 1, - "key": "ssh-rsa AAA...", - "url": "https://api.github.com/repos/octocat/Hello-World/keys/1", - "title": "octocat@octomac", - "verified": true, - "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" - } - ], + "example": {}, "schema": { "type": "array", "items": { @@ -164177,18 +164165,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -164302,9 +164278,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true }, "schema": { "title": "Deploy Key", @@ -164331,18 +164305,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -164432,9 +164394,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true }, "schema": { "title": "Deploy Key", @@ -164461,18 +164421,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -178146,19 +178094,6 @@ "created_at": { "type": "string", "format": "date-time" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ], - "format": "date-time" } }, "required": [ @@ -193835,9 +193770,10 @@ }, { "name": "ref", - "description": "

ref parameter

", + "description": "

The name of the fully qualified reference to update. For example, refs/heads/master. If the value doesn't start with refs and have at least two slashes, it will be rejected.

", "in": "path", "required": true, + "example": "refs/head/master", "schema": { "type": "string" }, @@ -194931,7 +194867,7 @@ } ], "previews": [], - "descriptionHTML": "

The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.

\n

If you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"Create a commit\" and \"Update a reference.\"

", + "descriptionHTML": "

The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.

\n

If you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"Create a commit\" and \"Update a reference.\"

\n

Returns an error if you try to delete a file that does not exist.

", "statusCodes": [ { "httpStatusCode": "201", @@ -305663,11 +305599,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The title of the new pull request.

", + "description": "

The title of the new pull request. Required unless issue is specified.

", "name": "title", "in": "body", "rawType": "string", - "rawDescription": "The title of the new pull request.", + "rawDescription": "The title of the new pull request. Required unless `issue` is specified.", "isRequired": false, "childParamsGroups": [] }, @@ -305723,13 +305659,14 @@ }, { "type": "integer", + "description": "

An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless title is specified.

", "examples": [ 1 ], "name": "issue", "in": "body", "rawType": "integer", - "description": "", + "rawDescription": "An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless `title` is specified.", "isRequired": false, "childParamsGroups": [] } @@ -309498,7 +309435,7 @@ } ], "previews": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "statusCodes": [ { "httpStatusCode": "201", @@ -321309,7 +321246,7 @@ "in": "body", "rawType": "string", "rawDescription": "The SHA of the commit needing a comment. Not using the latest commit SHA may render your comment outdated if a subsequent commit modifies the line you specify as the `position`.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -321319,7 +321256,7 @@ "in": "body", "rawType": "string", "rawDescription": "The relative path to the file that necessitates a comment.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -321357,7 +321294,7 @@ "in": "body", "rawType": "integer", "rawDescription": "The line of the blob in the pull request diff that the comment applies to. For a multi-line comment, the last line of the range that your comment applies to.", - "isRequired": false, + "isRequired": true, "childParamsGroups": [] }, { @@ -322649,7 +322586,7 @@ "serverUrl": "https://HOSTNAME/api/v3", "verb": "get", "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers", - "title": "List requested reviewers for a pull request", + "title": "Get all requested reviewers for a pull request", "category": "pulls", "subcategory": "review-requests", "parameters": [ @@ -322679,24 +322616,6 @@ "schema": { "type": "integer" } - }, - { - "name": "per_page", - "description": "

The number of results per page (max 100).

", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, - { - "name": "page", - "description": "

Page number of the results to fetch.

", - "in": "query", - "schema": { - "type": "integer", - "default": 1 - } } ], "bodyParameters": [], @@ -323139,7 +323058,7 @@ } ], "previews": [], - "descriptionHTML": "

Lists the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the List reviews for a pull request operation.

", + "descriptionHTML": "

Gets the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the List reviews for a pull request operation.

", "statusCodes": [ { "httpStatusCode": "200", @@ -338068,7 +337987,7 @@ } ], "previews": [], - "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", + "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", "statusCodes": [ { "httpStatusCode": "200", diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json index 92403a170e..460a6fa945 100644 --- a/lib/rest/static/dereferenced/api.github.com.deref.json +++ b/lib/rest/static/dereferenced/api.github.com.deref.json @@ -4719,7 +4719,7 @@ "examples": { "default": { "value": { - "respoitory": "Hello-World", + "repository": "Hello-World", "permissions": { "issues": "write", "contents": "read" @@ -52580,15 +52580,6 @@ "format": "date-time" } }, - { - "name": "per_page", - "description": "The number of results per page (max 100).", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, { "name": "page", "description": "Page number of the results to fetch.", @@ -52597,6 +52588,15 @@ "type": "integer", "default": 1 } + }, + { + "name": "per_page", + "description": "The number of results per page (max 50).", + "in": "query", + "schema": { + "type": "integer", + "default": 50 + } } ], "responses": { @@ -166384,7 +166384,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see \"[Create a check run](https://docs.github.com/rest/reference/checks#create-a-check-run).\"", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", "in": "query", "required": false, "schema": { @@ -187409,7 +187409,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see \"[Create a check run](https://docs.github.com/rest/reference/checks#create-a-check-run).\"", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", "in": "query", "required": false, "schema": { @@ -299694,9 +299694,10 @@ }, { "name": "ref", - "description": "ref parameter", + "description": "The name of the fully qualified reference to update. For example, `refs/heads/master`. If the value doesn't start with `refs` and have at least two slashes, it will be rejected.", "in": "path", "required": true, + "example": "refs/head/master", "schema": { "type": "string" }, @@ -300605,7 +300606,7 @@ "/repos/{owner}/{repo}/git/trees": { "post": { "summary": "Create a tree", - "description": "The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.\n\nIf you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"[Create a commit](https://docs.github.com/rest/reference/git#create-a-commit)\" and \"[Update a reference](https://docs.github.com/rest/reference/git#update-a-reference).\"", + "description": "The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.\n\nIf you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"[Create a commit](https://docs.github.com/rest/reference/git#create-a-commit)\" and \"[Update a reference](https://docs.github.com/rest/reference/git#update-a-reference).\"\n\nReturns an error if you try to delete a file that does not exist.", "tags": [ "git" ], @@ -394497,7 +394498,7 @@ }, "post": { "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -394535,7 +394536,7 @@ "properties": { "title": { "type": "string", - "description": "The title of the new pull request." + "description": "The title of the new pull request. Required unless `issue` is specified." }, "head": { "type": "string", @@ -394559,6 +394560,7 @@ }, "issue": { "type": "integer", + "description": "An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless `title` is specified.", "examples": [ 1 ] @@ -416257,7 +416259,10 @@ } }, "required": [ - "body" + "body", + "commit_id", + "path", + "line" ] }, "examples": { @@ -419154,15 +419159,15 @@ }, "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers": { "get": { - "summary": "List requested reviewers for a pull request", - "description": "Lists the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the [List reviews for a pull request](https://docs.github.com/rest/pulls/reviews#list-reviews-for-a-pull-request) operation.", + "summary": "Get all requested reviewers for a pull request", + "description": "Gets the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the [List reviews for a pull request](https://docs.github.com/rest/pulls/reviews#list-reviews-for-a-pull-request) operation.", "tags": [ "pulls" ], "operationId": "pulls/list-requested-reviewers", "externalDocs": { "description": "API method documentation", - "url": "https://docs.github.com/rest/reference/pulls#list-requested-reviewers-for-a-pull-request" + "url": "https://docs.github.com/rest/reference/pulls#get-all-requested-reviewers-for-a-pull-request" }, "parameters": [ { @@ -419191,24 +419196,6 @@ "schema": { "type": "integer" } - }, - { - "name": "per_page", - "description": "The number of results per page (max 100).", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, - { - "name": "page", - "description": "Page number of the results to fetch.", - "in": "query", - "schema": { - "type": "integer", - "default": 1 - } } ], "responses": { @@ -434351,7 +434338,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events": { "post": { "summary": "Submit a review for a pull request", - "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/rest/pulls#create-a-review-for-a-pull-request).\"", + "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/rest/pulls#create-a-review-for-a-pull-request).\"", "tags": [ "pulls" ], diff --git a/lib/rest/static/dereferenced/ghes-3.2.deref.json b/lib/rest/static/dereferenced/ghes-3.2.deref.json index 9e5135fa54..d6582458ce 100644 --- a/lib/rest/static/dereferenced/ghes-3.2.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.2.deref.json @@ -1267,19 +1267,6 @@ "created_at": { "type": "string", "format": "date-time" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ], - "format": "date-time" } }, "required": [ @@ -11371,7 +11358,7 @@ "examples": { "default": { "value": { - "respoitory": "Hello-World", + "repository": "Hello-World", "permissions": { "issues": "write", "contents": "read" @@ -62616,15 +62603,6 @@ "format": "date-time" } }, - { - "name": "per_page", - "description": "The number of results per page (max 100).", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, { "name": "page", "description": "Page number of the results to fetch.", @@ -62633,6 +62611,15 @@ "type": "integer", "default": 1 } + }, + { + "name": "per_page", + "description": "The number of results per page (max 50).", + "in": "query", + "schema": { + "type": "integer", + "default": 50 + } } ], "responses": { @@ -140711,7 +140698,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see \"[Create a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#create-a-check-run).\"", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", "in": "query", "required": false, "schema": { @@ -154347,7 +154334,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see \"[Create a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#create-a-check-run).\"", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", "in": "query", "required": false, "schema": { @@ -247599,9 +247586,10 @@ }, { "name": "ref", - "description": "ref parameter", + "description": "The name of the fully qualified reference to update. For example, `refs/heads/master`. If the value doesn't start with `refs` and have at least two slashes, it will be rejected.", "in": "path", "required": true, + "example": "refs/head/master", "schema": { "type": "string" }, @@ -248510,7 +248498,7 @@ "/repos/{owner}/{repo}/git/trees": { "post": { "summary": "Create a tree", - "description": "The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.\n\nIf you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"[Create a commit](https://docs.github.com/enterprise-server@3.2/rest/reference/git#create-a-commit)\" and \"[Update a reference](https://docs.github.com/enterprise-server@3.2/rest/reference/git#update-a-reference).\"", + "description": "The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.\n\nIf you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"[Create a commit](https://docs.github.com/enterprise-server@3.2/rest/reference/git#create-a-commit)\" and \"[Update a reference](https://docs.github.com/enterprise-server@3.2/rest/reference/git#update-a-reference).\"\n\nReturns an error if you try to delete a file that does not exist.", "tags": [ "git" ], @@ -323034,18 +323022,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -323061,19 +323037,8 @@ }, "examples": { "default": { - "value": [ - { - "id": 1, - "key": "ssh-rsa AAA...", - "url": "https://api.github.com/repos/octocat/Hello-World/keys/1", - "title": "octocat@octomac", - "verified": true, - "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" - } - ] + "value": { + } } } } @@ -323192,18 +323157,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -323225,9 +323178,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true } } } @@ -323397,18 +323348,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -323430,9 +323369,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true } } } @@ -339619,7 +339556,7 @@ }, "post": { "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -339657,7 +339594,7 @@ "properties": { "title": { "type": "string", - "description": "The title of the new pull request." + "description": "The title of the new pull request. Required unless `issue` is specified." }, "head": { "type": "string", @@ -339681,6 +339618,7 @@ }, "issue": { "type": "integer", + "description": "An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless `title` is specified.", "examples": [ 1 ] @@ -355342,7 +355280,10 @@ } }, "required": [ - "body" + "body", + "commit_id", + "path", + "line" ] }, "examples": { @@ -358245,15 +358186,15 @@ }, "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers": { "get": { - "summary": "List requested reviewers for a pull request", - "description": "Lists the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the [List reviews for a pull request](https://docs.github.com/enterprise-server@3.2/rest/pulls/reviews#list-reviews-for-a-pull-request) operation.", + "summary": "Get all requested reviewers for a pull request", + "description": "Gets the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the [List reviews for a pull request](https://docs.github.com/enterprise-server@3.2/rest/pulls/reviews#list-reviews-for-a-pull-request) operation.", "tags": [ "pulls" ], "operationId": "pulls/list-requested-reviewers", "externalDocs": { "description": "API method documentation", - "url": "https://docs.github.com/enterprise-server@3.2/rest/reference/pulls#list-requested-reviewers-for-a-pull-request" + "url": "https://docs.github.com/enterprise-server@3.2/rest/reference/pulls#get-all-requested-reviewers-for-a-pull-request" }, "parameters": [ { @@ -358282,24 +358223,6 @@ "schema": { "type": "integer" } - }, - { - "name": "per_page", - "description": "The number of results per page (max 100).", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, - { - "name": "page", - "description": "Page number of the results to fetch.", - "in": "query", - "schema": { - "type": "integer", - "default": 1 - } } ], "responses": { @@ -373366,7 +373289,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events": { "post": { "summary": "Submit a review for a pull request", - "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/enterprise-server@3.2/rest/pulls#create-a-review-for-a-pull-request).\"", + "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/enterprise-server@3.2/rest/pulls#create-a-review-for-a-pull-request).\"", "tags": [ "pulls" ], diff --git a/lib/rest/static/dereferenced/ghes-3.3.deref.json b/lib/rest/static/dereferenced/ghes-3.3.deref.json index 4cb2fa7891..f0020b2fe5 100644 --- a/lib/rest/static/dereferenced/ghes-3.3.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.3.deref.json @@ -1199,19 +1199,6 @@ "created_at": { "type": "string", "format": "date-time" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ], - "format": "date-time" } }, "required": [ @@ -11225,7 +11212,7 @@ "examples": { "default": { "value": { - "respoitory": "Hello-World", + "repository": "Hello-World", "permissions": { "issues": "write", "contents": "read" @@ -62928,15 +62915,6 @@ "format": "date-time" } }, - { - "name": "per_page", - "description": "The number of results per page (max 100).", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, { "name": "page", "description": "Page number of the results to fetch.", @@ -62945,6 +62923,15 @@ "type": "integer", "default": 1 } + }, + { + "name": "per_page", + "description": "The number of results per page (max 50).", + "in": "query", + "schema": { + "type": "integer", + "default": 50 + } } ], "responses": { @@ -142088,7 +142075,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see \"[Create a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#create-a-check-run).\"", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", "in": "query", "required": false, "schema": { @@ -155832,7 +155819,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see \"[Create a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#create-a-check-run).\"", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", "in": "query", "required": false, "schema": { @@ -249761,9 +249748,10 @@ }, { "name": "ref", - "description": "ref parameter", + "description": "The name of the fully qualified reference to update. For example, `refs/heads/master`. If the value doesn't start with `refs` and have at least two slashes, it will be rejected.", "in": "path", "required": true, + "example": "refs/head/master", "schema": { "type": "string" }, @@ -250672,7 +250660,7 @@ "/repos/{owner}/{repo}/git/trees": { "post": { "summary": "Create a tree", - "description": "The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.\n\nIf you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"[Create a commit](https://docs.github.com/enterprise-server@3.3/rest/reference/git#create-a-commit)\" and \"[Update a reference](https://docs.github.com/enterprise-server@3.3/rest/reference/git#update-a-reference).\"", + "description": "The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.\n\nIf you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"[Create a commit](https://docs.github.com/enterprise-server@3.3/rest/reference/git#create-a-commit)\" and \"[Update a reference](https://docs.github.com/enterprise-server@3.3/rest/reference/git#update-a-reference).\"\n\nReturns an error if you try to delete a file that does not exist.", "tags": [ "git" ], @@ -325223,18 +325211,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -325250,19 +325226,8 @@ }, "examples": { "default": { - "value": [ - { - "id": 1, - "key": "ssh-rsa AAA...", - "url": "https://api.github.com/repos/octocat/Hello-World/keys/1", - "title": "octocat@octomac", - "verified": true, - "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" - } - ] + "value": { + } } } } @@ -325381,18 +325346,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -325414,9 +325367,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true } } } @@ -325586,18 +325537,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -325619,9 +325558,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true } } } @@ -342004,7 +341941,7 @@ }, "post": { "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -342042,7 +341979,7 @@ "properties": { "title": { "type": "string", - "description": "The title of the new pull request." + "description": "The title of the new pull request. Required unless `issue` is specified." }, "head": { "type": "string", @@ -342066,6 +342003,7 @@ }, "issue": { "type": "integer", + "description": "An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless `title` is specified.", "examples": [ 1 ] @@ -357676,7 +357614,10 @@ } }, "required": [ - "body" + "body", + "commit_id", + "path", + "line" ] }, "examples": { @@ -360573,15 +360514,15 @@ }, "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers": { "get": { - "summary": "List requested reviewers for a pull request", - "description": "Lists the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the [List reviews for a pull request](https://docs.github.com/enterprise-server@3.3/rest/pulls/reviews#list-reviews-for-a-pull-request) operation.", + "summary": "Get all requested reviewers for a pull request", + "description": "Gets the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the [List reviews for a pull request](https://docs.github.com/enterprise-server@3.3/rest/pulls/reviews#list-reviews-for-a-pull-request) operation.", "tags": [ "pulls" ], "operationId": "pulls/list-requested-reviewers", "externalDocs": { "description": "API method documentation", - "url": "https://docs.github.com/enterprise-server@3.3/rest/reference/pulls#list-requested-reviewers-for-a-pull-request" + "url": "https://docs.github.com/enterprise-server@3.3/rest/reference/pulls#get-all-requested-reviewers-for-a-pull-request" }, "parameters": [ { @@ -360610,24 +360551,6 @@ "schema": { "type": "integer" } - }, - { - "name": "per_page", - "description": "The number of results per page (max 100).", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, - { - "name": "page", - "description": "Page number of the results to fetch.", - "in": "query", - "schema": { - "type": "integer", - "default": 1 - } } ], "responses": { @@ -375738,7 +375661,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events": { "post": { "summary": "Submit a review for a pull request", - "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/enterprise-server@3.3/rest/pulls#create-a-review-for-a-pull-request).\"", + "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/enterprise-server@3.3/rest/pulls#create-a-review-for-a-pull-request).\"", "tags": [ "pulls" ], diff --git a/lib/rest/static/dereferenced/ghes-3.4.deref.json b/lib/rest/static/dereferenced/ghes-3.4.deref.json index 2db5a8655d..50d852e450 100644 --- a/lib/rest/static/dereferenced/ghes-3.4.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.4.deref.json @@ -1199,19 +1199,6 @@ "created_at": { "type": "string", "format": "date-time" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ], - "format": "date-time" } }, "required": [ @@ -11177,7 +11164,7 @@ "examples": { "default": { "value": { - "respoitory": "Hello-World", + "repository": "Hello-World", "permissions": { "issues": "write", "contents": "read" @@ -63170,15 +63157,6 @@ "format": "date-time" } }, - { - "name": "per_page", - "description": "The number of results per page (max 100).", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, { "name": "page", "description": "Page number of the results to fetch.", @@ -63187,6 +63165,15 @@ "type": "integer", "default": 1 } + }, + { + "name": "per_page", + "description": "The number of results per page (max 50).", + "in": "query", + "schema": { + "type": "integer", + "default": 50 + } } ], "responses": { @@ -153239,7 +153226,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see \"[Create a check run](https://docs.github.com/enterprise-server@3.4/rest/reference/checks#create-a-check-run).\"", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", "in": "query", "required": false, "schema": { @@ -166983,7 +166970,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see \"[Create a check run](https://docs.github.com/enterprise-server@3.4/rest/reference/checks#create-a-check-run).\"", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", "in": "query", "required": false, "schema": { @@ -266317,9 +266304,10 @@ }, { "name": "ref", - "description": "ref parameter", + "description": "The name of the fully qualified reference to update. For example, `refs/heads/master`. If the value doesn't start with `refs` and have at least two slashes, it will be rejected.", "in": "path", "required": true, + "example": "refs/head/master", "schema": { "type": "string" }, @@ -267228,7 +267216,7 @@ "/repos/{owner}/{repo}/git/trees": { "post": { "summary": "Create a tree", - "description": "The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.\n\nIf you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"[Create a commit](https://docs.github.com/enterprise-server@3.4/rest/reference/git#create-a-commit)\" and \"[Update a reference](https://docs.github.com/enterprise-server@3.4/rest/reference/git#update-a-reference).\"", + "description": "The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.\n\nIf you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"[Create a commit](https://docs.github.com/enterprise-server@3.4/rest/reference/git#create-a-commit)\" and \"[Update a reference](https://docs.github.com/enterprise-server@3.4/rest/reference/git#update-a-reference).\"\n\nReturns an error if you try to delete a file that does not exist.", "tags": [ "git" ], @@ -341771,18 +341759,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -341798,19 +341774,8 @@ }, "examples": { "default": { - "value": [ - { - "id": 1, - "key": "ssh-rsa AAA...", - "url": "https://api.github.com/repos/octocat/Hello-World/keys/1", - "title": "octocat@octomac", - "verified": true, - "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" - } - ] + "value": { + } } } } @@ -341929,18 +341894,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -341962,9 +341915,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true } } } @@ -342134,18 +342085,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -342167,9 +342106,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true } } } @@ -358552,7 +358489,7 @@ }, "post": { "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.4/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.4/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.4/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.4/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -358590,7 +358527,7 @@ "properties": { "title": { "type": "string", - "description": "The title of the new pull request." + "description": "The title of the new pull request. Required unless `issue` is specified." }, "head": { "type": "string", @@ -358614,6 +358551,7 @@ }, "issue": { "type": "integer", + "description": "An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless `title` is specified.", "examples": [ 1 ] @@ -374224,7 +374162,10 @@ } }, "required": [ - "body" + "body", + "commit_id", + "path", + "line" ] }, "examples": { @@ -377121,15 +377062,15 @@ }, "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers": { "get": { - "summary": "List requested reviewers for a pull request", - "description": "Lists the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the [List reviews for a pull request](https://docs.github.com/enterprise-server@3.4/rest/pulls/reviews#list-reviews-for-a-pull-request) operation.", + "summary": "Get all requested reviewers for a pull request", + "description": "Gets the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the [List reviews for a pull request](https://docs.github.com/enterprise-server@3.4/rest/pulls/reviews#list-reviews-for-a-pull-request) operation.", "tags": [ "pulls" ], "operationId": "pulls/list-requested-reviewers", "externalDocs": { "description": "API method documentation", - "url": "https://docs.github.com/enterprise-server@3.4/rest/reference/pulls#list-requested-reviewers-for-a-pull-request" + "url": "https://docs.github.com/enterprise-server@3.4/rest/reference/pulls#get-all-requested-reviewers-for-a-pull-request" }, "parameters": [ { @@ -377158,24 +377099,6 @@ "schema": { "type": "integer" } - }, - { - "name": "per_page", - "description": "The number of results per page (max 100).", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, - { - "name": "page", - "description": "Page number of the results to fetch.", - "in": "query", - "schema": { - "type": "integer", - "default": 1 - } } ], "responses": { @@ -392286,7 +392209,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events": { "post": { "summary": "Submit a review for a pull request", - "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/enterprise-server@3.4/rest/pulls#create-a-review-for-a-pull-request).\"", + "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/enterprise-server@3.4/rest/pulls#create-a-review-for-a-pull-request).\"", "tags": [ "pulls" ], diff --git a/lib/rest/static/dereferenced/ghes-3.5.deref.json b/lib/rest/static/dereferenced/ghes-3.5.deref.json index 4bddbbaa0b..d19b07715d 100644 --- a/lib/rest/static/dereferenced/ghes-3.5.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.5.deref.json @@ -1199,19 +1199,6 @@ "created_at": { "type": "string", "format": "date-time" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ], - "format": "date-time" } }, "required": [ @@ -11177,7 +11164,7 @@ "examples": { "default": { "value": { - "respoitory": "Hello-World", + "repository": "Hello-World", "permissions": { "issues": "write", "contents": "read" @@ -63540,15 +63527,6 @@ "format": "date-time" } }, - { - "name": "per_page", - "description": "The number of results per page (max 100).", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, { "name": "page", "description": "Page number of the results to fetch.", @@ -63557,6 +63535,15 @@ "type": "integer", "default": 1 } + }, + { + "name": "per_page", + "description": "The number of results per page (max 50).", + "in": "query", + "schema": { + "type": "integer", + "default": 50 + } } ], "responses": { @@ -155997,7 +155984,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see \"[Create a check run](https://docs.github.com/enterprise-server@3.5/rest/reference/checks#create-a-check-run).\"", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", "in": "query", "required": false, "schema": { @@ -176460,7 +176447,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see \"[Create a check run](https://docs.github.com/enterprise-server@3.5/rest/reference/checks#create-a-check-run).\"", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", "in": "query", "required": false, "schema": { @@ -276438,9 +276425,10 @@ }, { "name": "ref", - "description": "ref parameter", + "description": "The name of the fully qualified reference to update. For example, `refs/heads/master`. If the value doesn't start with `refs` and have at least two slashes, it will be rejected.", "in": "path", "required": true, + "example": "refs/head/master", "schema": { "type": "string" }, @@ -277349,7 +277337,7 @@ "/repos/{owner}/{repo}/git/trees": { "post": { "summary": "Create a tree", - "description": "The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.\n\nIf you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"[Create a commit](https://docs.github.com/enterprise-server@3.5/rest/reference/git#create-a-commit)\" and \"[Update a reference](https://docs.github.com/enterprise-server@3.5/rest/reference/git#update-a-reference).\"", + "description": "The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.\n\nIf you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"[Create a commit](https://docs.github.com/enterprise-server@3.5/rest/reference/git#create-a-commit)\" and \"[Update a reference](https://docs.github.com/enterprise-server@3.5/rest/reference/git#update-a-reference).\"\n\nReturns an error if you try to delete a file that does not exist.", "tags": [ "git" ], @@ -351904,18 +351892,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -351931,19 +351907,8 @@ }, "examples": { "default": { - "value": [ - { - "id": 1, - "key": "ssh-rsa AAA...", - "url": "https://api.github.com/repos/octocat/Hello-World/keys/1", - "title": "octocat@octomac", - "verified": true, - "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" - } - ] + "value": { + } } } } @@ -352062,18 +352027,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -352095,9 +352048,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true } } } @@ -352267,18 +352218,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -352300,9 +352239,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true } } } @@ -368691,7 +368628,7 @@ }, "post": { "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.5/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.5/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.5/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.5/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -368729,7 +368666,7 @@ "properties": { "title": { "type": "string", - "description": "The title of the new pull request." + "description": "The title of the new pull request. Required unless `issue` is specified." }, "head": { "type": "string", @@ -368753,6 +368690,7 @@ }, "issue": { "type": "integer", + "description": "An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless `title` is specified.", "examples": [ 1 ] @@ -384363,7 +384301,10 @@ } }, "required": [ - "body" + "body", + "commit_id", + "path", + "line" ] }, "examples": { @@ -387260,15 +387201,15 @@ }, "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers": { "get": { - "summary": "List requested reviewers for a pull request", - "description": "Lists the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the [List reviews for a pull request](https://docs.github.com/enterprise-server@3.5/rest/pulls/reviews#list-reviews-for-a-pull-request) operation.", + "summary": "Get all requested reviewers for a pull request", + "description": "Gets the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the [List reviews for a pull request](https://docs.github.com/enterprise-server@3.5/rest/pulls/reviews#list-reviews-for-a-pull-request) operation.", "tags": [ "pulls" ], "operationId": "pulls/list-requested-reviewers", "externalDocs": { "description": "API method documentation", - "url": "https://docs.github.com/enterprise-server@3.5/rest/reference/pulls#list-requested-reviewers-for-a-pull-request" + "url": "https://docs.github.com/enterprise-server@3.5/rest/reference/pulls#get-all-requested-reviewers-for-a-pull-request" }, "parameters": [ { @@ -387297,24 +387238,6 @@ "schema": { "type": "integer" } - }, - { - "name": "per_page", - "description": "The number of results per page (max 100).", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, - { - "name": "page", - "description": "Page number of the results to fetch.", - "in": "query", - "schema": { - "type": "integer", - "default": 1 - } } ], "responses": { @@ -402425,7 +402348,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events": { "post": { "summary": "Submit a review for a pull request", - "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/enterprise-server@3.5/rest/pulls#create-a-review-for-a-pull-request).\"", + "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/enterprise-server@3.5/rest/pulls#create-a-review-for-a-pull-request).\"", "tags": [ "pulls" ], diff --git a/lib/rest/static/dereferenced/ghes-3.6.deref.json b/lib/rest/static/dereferenced/ghes-3.6.deref.json index d9789cd36e..9216987f4f 100644 --- a/lib/rest/static/dereferenced/ghes-3.6.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.6.deref.json @@ -1199,19 +1199,6 @@ "created_at": { "type": "string", "format": "date-time" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ], - "format": "date-time" } }, "required": [ @@ -11177,7 +11164,7 @@ "examples": { "default": { "value": { - "respoitory": "Hello-World", + "repository": "Hello-World", "permissions": { "issues": "write", "contents": "read" @@ -63978,15 +63965,6 @@ "format": "date-time" } }, - { - "name": "per_page", - "description": "The number of results per page (max 100).", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, { "name": "page", "description": "Page number of the results to fetch.", @@ -63995,6 +63973,15 @@ "type": "integer", "default": 1 } + }, + { + "name": "per_page", + "description": "The number of results per page (max 50).", + "in": "query", + "schema": { + "type": "integer", + "default": 50 + } } ], "responses": { @@ -157088,7 +157075,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see \"[Create a check run](https://docs.github.com/enterprise-server@3.6/rest/reference/checks#create-a-check-run).\"", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", "in": "query", "required": false, "schema": { @@ -177760,7 +177747,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see \"[Create a check run](https://docs.github.com/enterprise-server@3.6/rest/reference/checks#create-a-check-run).\"", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", "in": "query", "required": false, "schema": { @@ -278236,9 +278223,10 @@ }, { "name": "ref", - "description": "ref parameter", + "description": "The name of the fully qualified reference to update. For example, `refs/heads/master`. If the value doesn't start with `refs` and have at least two slashes, it will be rejected.", "in": "path", "required": true, + "example": "refs/head/master", "schema": { "type": "string" }, @@ -279147,7 +279135,7 @@ "/repos/{owner}/{repo}/git/trees": { "post": { "summary": "Create a tree", - "description": "The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.\n\nIf you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"[Create a commit](https://docs.github.com/enterprise-server@3.6/rest/reference/git#create-a-commit)\" and \"[Update a reference](https://docs.github.com/enterprise-server@3.6/rest/reference/git#update-a-reference).\"", + "description": "The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.\n\nIf you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"[Create a commit](https://docs.github.com/enterprise-server@3.6/rest/reference/git#create-a-commit)\" and \"[Update a reference](https://docs.github.com/enterprise-server@3.6/rest/reference/git#update-a-reference).\"\n\nReturns an error if you try to delete a file that does not exist.", "tags": [ "git" ], @@ -353790,18 +353778,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -353817,19 +353793,8 @@ }, "examples": { "default": { - "value": [ - { - "id": 1, - "key": "ssh-rsa AAA...", - "url": "https://api.github.com/repos/octocat/Hello-World/keys/1", - "title": "octocat@octomac", - "verified": true, - "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" - } - ] + "value": { + } } } } @@ -353948,18 +353913,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -353981,9 +353934,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true } } } @@ -354153,18 +354104,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -354186,9 +354125,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true } } } @@ -370601,7 +370538,7 @@ }, "post": { "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.6/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.6/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.6/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.6/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -370639,7 +370576,7 @@ "properties": { "title": { "type": "string", - "description": "The title of the new pull request." + "description": "The title of the new pull request. Required unless `issue` is specified." }, "head": { "type": "string", @@ -370663,6 +370600,7 @@ }, "issue": { "type": "integer", + "description": "An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless `title` is specified.", "examples": [ 1 ] @@ -386273,7 +386211,10 @@ } }, "required": [ - "body" + "body", + "commit_id", + "path", + "line" ] }, "examples": { @@ -389170,15 +389111,15 @@ }, "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers": { "get": { - "summary": "List requested reviewers for a pull request", - "description": "Lists the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the [List reviews for a pull request](https://docs.github.com/enterprise-server@3.6/rest/pulls/reviews#list-reviews-for-a-pull-request) operation.", + "summary": "Get all requested reviewers for a pull request", + "description": "Gets the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the [List reviews for a pull request](https://docs.github.com/enterprise-server@3.6/rest/pulls/reviews#list-reviews-for-a-pull-request) operation.", "tags": [ "pulls" ], "operationId": "pulls/list-requested-reviewers", "externalDocs": { "description": "API method documentation", - "url": "https://docs.github.com/enterprise-server@3.6/rest/reference/pulls#list-requested-reviewers-for-a-pull-request" + "url": "https://docs.github.com/enterprise-server@3.6/rest/reference/pulls#get-all-requested-reviewers-for-a-pull-request" }, "parameters": [ { @@ -389207,24 +389148,6 @@ "schema": { "type": "integer" } - }, - { - "name": "per_page", - "description": "The number of results per page (max 100).", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, - { - "name": "page", - "description": "Page number of the results to fetch.", - "in": "query", - "schema": { - "type": "integer", - "default": 1 - } } ], "responses": { @@ -404367,7 +404290,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events": { "post": { "summary": "Submit a review for a pull request", - "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/enterprise-server@3.6/rest/pulls#create-a-review-for-a-pull-request).\"", + "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/enterprise-server@3.6/rest/pulls#create-a-review-for-a-pull-request).\"", "tags": [ "pulls" ], diff --git a/lib/rest/static/dereferenced/github.ae.deref.json b/lib/rest/static/dereferenced/github.ae.deref.json index 717dd25b5b..a42a92a1cb 100644 --- a/lib/rest/static/dereferenced/github.ae.deref.json +++ b/lib/rest/static/dereferenced/github.ae.deref.json @@ -1195,19 +1195,6 @@ "created_at": { "type": "string", "format": "date-time" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ], - "format": "date-time" } }, "required": [ @@ -9307,7 +9294,7 @@ "examples": { "default": { "value": { - "respoitory": "Hello-World", + "repository": "Hello-World", "permissions": { "issues": "write", "contents": "read" @@ -41960,15 +41947,6 @@ "format": "date-time" } }, - { - "name": "per_page", - "description": "The number of results per page (max 100).", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, { "name": "page", "description": "Page number of the results to fetch.", @@ -41977,6 +41955,15 @@ "type": "integer", "default": 1 } + }, + { + "name": "per_page", + "description": "The number of results per page (max 50).", + "in": "query", + "schema": { + "type": "integer", + "default": 50 + } } ], "responses": { @@ -118755,7 +118742,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see \"[Create a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#create-a-check-run).\"", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", "in": "query", "required": false, "schema": { @@ -137779,7 +137766,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see \"[Create a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#create-a-check-run).\"", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", "in": "query", "required": false, "schema": { @@ -234400,9 +234387,10 @@ }, { "name": "ref", - "description": "ref parameter", + "description": "The name of the fully qualified reference to update. For example, `refs/heads/master`. If the value doesn't start with `refs` and have at least two slashes, it will be rejected.", "in": "path", "required": true, + "example": "refs/head/master", "schema": { "type": "string" }, @@ -235311,7 +235299,7 @@ "/repos/{owner}/{repo}/git/trees": { "post": { "summary": "Create a tree", - "description": "The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.\n\nIf you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"[Create a commit](https://docs.github.com/github-ae@latest/rest/reference/git#create-a-commit)\" and \"[Update a reference](https://docs.github.com/github-ae@latest/rest/reference/git#update-a-reference).\"", + "description": "The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.\n\nIf you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see \"[Create a commit](https://docs.github.com/github-ae@latest/rest/reference/git#create-a-commit)\" and \"[Update a reference](https://docs.github.com/github-ae@latest/rest/reference/git#update-a-reference).\"\n\nReturns an error if you try to delete a file that does not exist.", "tags": [ "git" ], @@ -309895,18 +309883,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -309922,19 +309898,8 @@ }, "examples": { "default": { - "value": [ - { - "id": 1, - "key": "ssh-rsa AAA...", - "url": "https://api.github.com/repos/octocat/Hello-World/keys/1", - "title": "octocat@octomac", - "verified": true, - "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" - } - ] + "value": { + } } } } @@ -310053,18 +310018,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -310086,9 +310039,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true } } } @@ -310258,18 +310209,6 @@ }, "read_only": { "type": "boolean" - }, - "added_by": { - "type": [ - "string", - "null" - ] - }, - "last_used": { - "type": [ - "string", - "null" - ] } }, "required": [ @@ -310291,9 +310230,7 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true, - "added_by": "octocat", - "last_used": "2022-01-10T15:53:42Z" + "read_only": true } } } @@ -326277,7 +326214,7 @@ }, "post": { "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -326315,7 +326252,7 @@ "properties": { "title": { "type": "string", - "description": "The title of the new pull request." + "description": "The title of the new pull request. Required unless `issue` is specified." }, "head": { "type": "string", @@ -326339,6 +326276,7 @@ }, "issue": { "type": "integer", + "description": "An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request. Required unless `title` is specified.", "examples": [ 1 ] @@ -341964,7 +341902,10 @@ } }, "required": [ - "body" + "body", + "commit_id", + "path", + "line" ] }, "examples": { @@ -344861,15 +344802,15 @@ }, "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers": { "get": { - "summary": "List requested reviewers for a pull request", - "description": "Lists the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the [List reviews for a pull request](https://docs.github.com/github-ae@latest/rest/pulls/reviews#list-reviews-for-a-pull-request) operation.", + "summary": "Get all requested reviewers for a pull request", + "description": "Gets the users or teams whose review is requested for a pull request. Once a requested reviewer submits a review, they are no longer considered a requested reviewer. Their review will instead be returned by the [List reviews for a pull request](https://docs.github.com/github-ae@latest/rest/pulls/reviews#list-reviews-for-a-pull-request) operation.", "tags": [ "pulls" ], "operationId": "pulls/list-requested-reviewers", "externalDocs": { "description": "API method documentation", - "url": "https://docs.github.com/github-ae@latest/rest/reference/pulls#list-requested-reviewers-for-a-pull-request" + "url": "https://docs.github.com/github-ae@latest/rest/reference/pulls#get-all-requested-reviewers-for-a-pull-request" }, "parameters": [ { @@ -344898,24 +344839,6 @@ "schema": { "type": "integer" } - }, - { - "name": "per_page", - "description": "The number of results per page (max 100).", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - } - }, - { - "name": "page", - "description": "Page number of the results to fetch.", - "in": "query", - "schema": { - "type": "integer", - "default": 1 - } } ], "responses": { @@ -360026,7 +359949,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events": { "post": { "summary": "Submit a review for a pull request", - "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/github-ae@latest/rest/pulls#create-a-review-for-a-pull-request).\"", + "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/github-ae@latest/rest/pulls#create-a-review-for-a-pull-request).\"", "tags": [ "pulls" ], diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br index 813952a00c..53569e0412 100644 --- a/lib/search/indexes/github-docs-3.2-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bd3054b030ec008d7df09049fda548417ebfc79686fcaf4befc17d540ab2e791 -size 794385 +oid sha256:6f75699764e1ee2e54293ae9a4e70496c71f94cf7397dc56590779b09fd21dcb +size 794217 diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br index 90b3918e8e..c3cc765c86 100644 --- a/lib/search/indexes/github-docs-3.2-cn.json.br +++ b/lib/search/indexes/github-docs-3.2-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:15ec3a3958adeb3eac5ef14ed30c4a532c0a8815b9603c74f129dd7b3f0f7a90 -size 1636346 +oid sha256:7b208d860f7b1144f0cec445f8571415deb2b42d3e4eb34e506a06b3dac3629a +size 1637943 diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br index 1c30cebb16..5b950f0fe9 100644 --- a/lib/search/indexes/github-docs-3.2-en-records.json.br +++ b/lib/search/indexes/github-docs-3.2-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ad2bcd6de9db27fb054dd5f3f1b26a65dd0fdb7b47b96bfd83515c6d3a5415e8 -size 1089379 +oid sha256:8f10ad0e05fba5b807c082e61f98ffe056393c2cfd4f9b714e028e2740e8455c +size 1089612 diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br index 5803c54f5e..3554830604 100644 --- a/lib/search/indexes/github-docs-3.2-en.json.br +++ b/lib/search/indexes/github-docs-3.2-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:84aeab8edea2e3fe815a777bdafc2dd2158371cfd5b0e317976011e7869b13eb -size 4415857 +oid sha256:d4b343400cc7aef05fdcfc93fac26da493d5f7d2bba524426a13a682d973b578 +size 4416324 diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br index fa6e31e7ef..ee28eba809 100644 --- a/lib/search/indexes/github-docs-3.2-es-records.json.br +++ b/lib/search/indexes/github-docs-3.2-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0b1f8ba4623312a7d09c576668f8c475f9c3c5a56dbf8ecc3ff6d472a3cd9223 -size 733865 +oid sha256:9b8dca7b9bba3a84c1e0af4413c7b5b8494b72c53dedd5fee28cecbca732316c +size 733369 diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br index a49027f657..a3d3db0585 100644 --- a/lib/search/indexes/github-docs-3.2-es.json.br +++ b/lib/search/indexes/github-docs-3.2-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:502f72c288478f2dbb70ce57605a22b9966ad4834f37ce35d65e339768c852cc -size 3130975 +oid sha256:e297b9de317ea5dfdbee27b4c1d4f6dba6774e2a63ef9abd34b2e610be77c06e +size 3126093 diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br index ef80f9a96b..06c12e3228 100644 --- a/lib/search/indexes/github-docs-3.2-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:52af056bbad9cf34d8aadccbf4553721a8937ad5a35d8047de59761d398fd57e -size 808750 +oid sha256:6efafd8da7af4e94333d5b53615ae9174a796b62bca6fdd709c92e057d977b61 +size 807922 diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br index 997d975611..2363cb919f 100644 --- a/lib/search/indexes/github-docs-3.2-ja.json.br +++ b/lib/search/indexes/github-docs-3.2-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:74f81ca5149c1001af580a8d70759bf7f6c2b02709d66eacfdbbc9d0cafd7001 -size 4448046 +oid sha256:8208229b9d1850349aedbd39269a19acaefd0180fd4d6e4d21eb29eb2f785a0b +size 4445240 diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br index df5213e560..4f321b7325 100644 --- a/lib/search/indexes/github-docs-3.2-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fb33f9191102e91f865baaad113c5760fca052da08de0b9124da24bef94a7922 -size 722361 +oid sha256:138969d9bf9fc9ec9be245cb7ab3003da2a43f6e1c0d4b5a0ba3e9a738abae54 +size 722217 diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br index fe97569367..ac5c18bfb0 100644 --- a/lib/search/indexes/github-docs-3.2-pt.json.br +++ b/lib/search/indexes/github-docs-3.2-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:503724e7a4f7b07880bf773107efa5d0dca89f905ab132924fc51a2662950ef7 -size 3028450 +oid sha256:c2408cb87285270711812caaef6976c43059bff8f57e33d2007bd19f2c3f388e +size 3027647 diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br index 95f06c6adc..8aa759759d 100644 --- a/lib/search/indexes/github-docs-3.3-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8deea3941494e7ff55bf48500a179d717037ff6128975b43ee4e7f675551656e -size 819578 +oid sha256:f062c46279fd407a30a9890d0e0de34103d37d89d467a49a8961e9c019a63b0c +size 819435 diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br index 673458847b..39e9a35c55 100644 --- a/lib/search/indexes/github-docs-3.3-cn.json.br +++ b/lib/search/indexes/github-docs-3.3-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:75ac97bf12fe195bcf59b2251b9b50ae1b3f86bdabe93d60a5e65b0ce380f0ae -size 1684325 +oid sha256:313c6f74f6a8c6b37d51f3d942943b5cbd8ef8b8a5deb66db694aab897e8ed80 +size 1684985 diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br index 68e493c216..9cb9bc4a1f 100644 --- a/lib/search/indexes/github-docs-3.3-en-records.json.br +++ b/lib/search/indexes/github-docs-3.3-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7e801da386fb91c7578d33566732a7da4abbfbaf034b1987aeb0dfeba22567a4 -size 1124613 +oid sha256:554b55a11923517ecc1e97ecdaaf04114bd05571492dbfe78b23a529998f4a8f +size 1124189 diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br index 6f855def6f..0ed98b5571 100644 --- a/lib/search/indexes/github-docs-3.3-en.json.br +++ b/lib/search/indexes/github-docs-3.3-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:531bb089ce86db9302b415f3ed219a61a5f6e3b54f46771f491eabad42f14436 -size 4521947 +oid sha256:9081de81f3ca34e7d380161bc6dbd3df89dccd57c0ec99d487c6ee2a4d794fa4 +size 4520994 diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br index ad33505b41..8aed02f7a8 100644 --- a/lib/search/indexes/github-docs-3.3-es-records.json.br +++ b/lib/search/indexes/github-docs-3.3-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f3ac4348968f7bd55349a3e4032226d83f6732aa0b9359d7a5faf0db09502d7e -size 754937 +oid sha256:052ba9b9f5ec35ff9184c88ff8e25ef729046bf5e3d441ee34e5b90dd6f8f0bd +size 754665 diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br index 96a7e34022..d5cd82801d 100644 --- a/lib/search/indexes/github-docs-3.3-es.json.br +++ b/lib/search/indexes/github-docs-3.3-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:540eff3744a4ddbe77cfc07777921f4ceae6e609fbccae109d5465198a46b7b7 -size 3217380 +oid sha256:e861467ff34fb5667daed2c6945df9110f9d387101ec64945a75dcef5ca3bd54 +size 3210655 diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br index 2a92cc048b..2de8138f22 100644 --- a/lib/search/indexes/github-docs-3.3-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:19de45fb9362fd481f0a3c6bcf98c6f2152df95bfbc431075f02746b1c3b22e2 -size 834182 +oid sha256:3d563222b504475efe3381778733d12a859230f629b30c00c4e60b4639988144 +size 833640 diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br index 6a4b5526b3..8cad5f876b 100644 --- a/lib/search/indexes/github-docs-3.3-ja.json.br +++ b/lib/search/indexes/github-docs-3.3-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2f428cc5ed39a4ffc5f827060360aa0d63cc4bcac45c75ab07f6578399c4dff2 -size 4583688 +oid sha256:7adf81cb36a577805b3e37ec65db155341e6814d3357d4c8d5291809cce03558 +size 4581310 diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br index e5dc1178f0..53ae3b1509 100644 --- a/lib/search/indexes/github-docs-3.3-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:aef2924d191ff717ff27b80ffeba8c5dc34deb1e33bf0eddf1ee3ad6041c81ad -size 743853 +oid sha256:d31bed03e6d1c151998824af5b7c1f5c11ad99389e63b71ec772d64e7ad6bb06 +size 743656 diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br index e88fd4ad53..ccffd3461e 100644 --- a/lib/search/indexes/github-docs-3.3-pt.json.br +++ b/lib/search/indexes/github-docs-3.3-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:77cc1df2bc33d36c054f82cb365ebca6569857d735e7e16fc630302eee485861 -size 3113254 +oid sha256:3db534814badbf8487e855cc5d230fd48567ce87caad8cb6e94ec3494031070f +size 3112859 diff --git a/lib/search/indexes/github-docs-3.4-cn-records.json.br b/lib/search/indexes/github-docs-3.4-cn-records.json.br index 3fa19ba4a7..7608311edc 100644 --- a/lib/search/indexes/github-docs-3.4-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.4-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f2a240e2d1a8229923aadd9e4f6603386b8e235c9b585e4dea3159215c2dc3ea -size 822193 +oid sha256:24aec8432e1b43aa32ad3c1d9c1e797ca2e38cfaa34300fafba13f4dc8cbc1d5 +size 822184 diff --git a/lib/search/indexes/github-docs-3.4-cn.json.br b/lib/search/indexes/github-docs-3.4-cn.json.br index bcbf04e63c..e64bd8219a 100644 --- a/lib/search/indexes/github-docs-3.4-cn.json.br +++ b/lib/search/indexes/github-docs-3.4-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7aa0b3e6687ed56ede3abf08636360f468e496856312be6eb98225821fd35f57 -size 1699288 +oid sha256:bfb93eec5d80ae787f650000f09acd8dca1945e0605ae5850a39234d741e3ad8 +size 1700591 diff --git a/lib/search/indexes/github-docs-3.4-en-records.json.br b/lib/search/indexes/github-docs-3.4-en-records.json.br index 3a64b79a2a..79343f34be 100644 --- a/lib/search/indexes/github-docs-3.4-en-records.json.br +++ b/lib/search/indexes/github-docs-3.4-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:81c80033e901b97ddb1e847327aeb0857b05e90742cb20050a0dd9d6d90f1d9f -size 1135570 +oid sha256:582ec20aefb752932e4663ea5ee2114145d91909bfdcb205c6a39efe23c6e608 +size 1135468 diff --git a/lib/search/indexes/github-docs-3.4-en.json.br b/lib/search/indexes/github-docs-3.4-en.json.br index cdaa99a3a6..386c3b0b2a 100644 --- a/lib/search/indexes/github-docs-3.4-en.json.br +++ b/lib/search/indexes/github-docs-3.4-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:086de113f35f54ca6a996e7e0623235e7a03d370f10bbe4bbdd12348675fc3e2 -size 4577573 +oid sha256:4855e87826462866d6095c24fc70830e2e4973f533cff4fd09629f49ee3a74fe +size 4578145 diff --git a/lib/search/indexes/github-docs-3.4-es-records.json.br b/lib/search/indexes/github-docs-3.4-es-records.json.br index ea1236f741..c5209bf85c 100644 --- a/lib/search/indexes/github-docs-3.4-es-records.json.br +++ b/lib/search/indexes/github-docs-3.4-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:96bbbc0ac2bcac52a4233b35e2152e702573229657b4f45dc17a299f5e4c8759 -size 759341 +oid sha256:8db91fbd484562c34dac2c629517f051fc04446cec8f4d5d93ceda03aaf5baf7 +size 759075 diff --git a/lib/search/indexes/github-docs-3.4-es.json.br b/lib/search/indexes/github-docs-3.4-es.json.br index ec358b0c85..3a1d264121 100644 --- a/lib/search/indexes/github-docs-3.4-es.json.br +++ b/lib/search/indexes/github-docs-3.4-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:101c5765e9f0693aaf648528118292a03fdb482c822ad384c77073fc868c3f76 -size 3239901 +oid sha256:f79f5626232989f3026629aa2a22fa7589857597aaeb20404604ba0b699ae95e +size 3233463 diff --git a/lib/search/indexes/github-docs-3.4-ja-records.json.br b/lib/search/indexes/github-docs-3.4-ja-records.json.br index 7968167619..bcc6086bc6 100644 --- a/lib/search/indexes/github-docs-3.4-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.4-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:72b8e188075b52f2a774441b43d3c34aa50e073dffe84faeec22688453442f8c -size 837643 +oid sha256:4c12f9ec2f630ac9245cf685694e3f9ab7b23afbe5ca7abb3e4a071377b50a56 +size 836688 diff --git a/lib/search/indexes/github-docs-3.4-ja.json.br b/lib/search/indexes/github-docs-3.4-ja.json.br index 3f6562e41f..4a167a3cf6 100644 --- a/lib/search/indexes/github-docs-3.4-ja.json.br +++ b/lib/search/indexes/github-docs-3.4-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4645621391ac4966edf0cf6375b3fdffe1d4ab5fec7fd0309137e46aaf637404 -size 4618546 +oid sha256:050ac777c61938b6109a6f68f9701d8e49d1741422af433f3ab31b500212ff9e +size 4615930 diff --git a/lib/search/indexes/github-docs-3.4-pt-records.json.br b/lib/search/indexes/github-docs-3.4-pt-records.json.br index f07ad42c25..b1b8719a25 100644 --- a/lib/search/indexes/github-docs-3.4-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.4-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c27b0748cb0a6539b7bb9ae1497768e003058d3d6fbae94ad5c8f18b6d8c13b5 -size 748029 +oid sha256:5047d287caaa48795edadb631a37dd9fa8076becc341a66a40a0f29ee59d6c6f +size 747944 diff --git a/lib/search/indexes/github-docs-3.4-pt.json.br b/lib/search/indexes/github-docs-3.4-pt.json.br index b61f42a0e1..fafffd0cc3 100644 --- a/lib/search/indexes/github-docs-3.4-pt.json.br +++ b/lib/search/indexes/github-docs-3.4-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1e8fdf084009d76c178a8b2613a608e95b45fdf165493c114a04d89c12aa0bf9 -size 3137852 +oid sha256:bfbf56c35e4f2e5f782fdc5e1d0465925f4d2516e4ffbf24bcb6cfb55f5c36ae +size 3137402 diff --git a/lib/search/indexes/github-docs-3.5-cn-records.json.br b/lib/search/indexes/github-docs-3.5-cn-records.json.br index f2399b9939..f9a6cdd7fd 100644 --- a/lib/search/indexes/github-docs-3.5-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.5-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:cbcf5c0bf83babfe878d2e5e253e00f0407b11ab4a2991ab7bee52741e4b520d -size 851696 +oid sha256:28a3f39e6b0e09aa9b4a149fa2bd44c343775ef8272a6353caeac0ae177f6cba +size 851594 diff --git a/lib/search/indexes/github-docs-3.5-cn.json.br b/lib/search/indexes/github-docs-3.5-cn.json.br index d44c2e977d..f3efc91d9f 100644 --- a/lib/search/indexes/github-docs-3.5-cn.json.br +++ b/lib/search/indexes/github-docs-3.5-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8561675c11f177e3a718e55155c462f320d4286bd80ee21894ea7dffe93fc947 -size 1759584 +oid sha256:9a2cc2a8c6d90b177b6d3eff1439a203c2840b1b4bc97f5c0f71246beec24aa1 +size 1759510 diff --git a/lib/search/indexes/github-docs-3.5-en-records.json.br b/lib/search/indexes/github-docs-3.5-en-records.json.br index 7e939e43f3..eb1289650c 100644 --- a/lib/search/indexes/github-docs-3.5-en-records.json.br +++ b/lib/search/indexes/github-docs-3.5-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6a25efaad9295507a45ff1832b3219d6ad04a9aaa0c1a9de4fa0cda887ebfc4d -size 1174270 +oid sha256:4b0b00c41538a647c282801765c7e2ab15f56151df07ab1fcee7f0e346bc9f8e +size 1174234 diff --git a/lib/search/indexes/github-docs-3.5-en.json.br b/lib/search/indexes/github-docs-3.5-en.json.br index ef15be2e04..8588ce3c4c 100644 --- a/lib/search/indexes/github-docs-3.5-en.json.br +++ b/lib/search/indexes/github-docs-3.5-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c86659be747dd6995c72facb6c570986799e592b1f8c9f4d1cb6a1db07b35273 -size 4737884 +oid sha256:c05f65430c02d88f130fb3f211479d6789e97ad96316009d69f6a3e11c630014 +size 4737252 diff --git a/lib/search/indexes/github-docs-3.5-es-records.json.br b/lib/search/indexes/github-docs-3.5-es-records.json.br index e016acdc58..ab85de1042 100644 --- a/lib/search/indexes/github-docs-3.5-es-records.json.br +++ b/lib/search/indexes/github-docs-3.5-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:90ab6db0e0e41988378be0d3c7ca212443590e69b81d1a4e1b9c8759341776cf -size 782685 +oid sha256:9a95a80ba264f6ae104a54a59e2a37e09708ad647ac864ce6c97a516aa13352d +size 782137 diff --git a/lib/search/indexes/github-docs-3.5-es.json.br b/lib/search/indexes/github-docs-3.5-es.json.br index 9170c223bf..652de4c72a 100644 --- a/lib/search/indexes/github-docs-3.5-es.json.br +++ b/lib/search/indexes/github-docs-3.5-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:75a8b2c0e938e4f6947a7cba21400a7f6e455339aac347cb01de1385d574b936 -size 3354240 +oid sha256:a3c9f90edb1074e87e5c46606a77a6b32dbaba2579f9b063686e64822a243f2c +size 3346487 diff --git a/lib/search/indexes/github-docs-3.5-ja-records.json.br b/lib/search/indexes/github-docs-3.5-ja-records.json.br index dfa18f5769..bf481b72bb 100644 --- a/lib/search/indexes/github-docs-3.5-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.5-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:384e100902ba3da3961888fe250020bc76f95227e2f36b3fcdd0eda2f1e9dac5 -size 864769 +oid sha256:8d918360005665773032633404120bd27712bc6bf68b542c88b9234502191aff +size 863942 diff --git a/lib/search/indexes/github-docs-3.5-ja.json.br b/lib/search/indexes/github-docs-3.5-ja.json.br index f54bf18713..b4a6f6c34b 100644 --- a/lib/search/indexes/github-docs-3.5-ja.json.br +++ b/lib/search/indexes/github-docs-3.5-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:06ec78d38d666274d2c23ac8f077aeafddf8ffe867bf63696d4a9eab0c4d1552 -size 4781105 +oid sha256:b9d5bb3e2b1bde9301ca4976ccd00699aca1ae701e93f8e696e2dc0fecc875c5 +size 4779668 diff --git a/lib/search/indexes/github-docs-3.5-pt-records.json.br b/lib/search/indexes/github-docs-3.5-pt-records.json.br index 1e3e786f5b..52bd865cfb 100644 --- a/lib/search/indexes/github-docs-3.5-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.5-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fb3e4e4b96893b13f1377f12950a74d21278f0325f1e695ec35d4477dfe13ff8 -size 770794 +oid sha256:2a09356d91ad1c6db8a230b44f6e9c8cf5fb63d936140637e6af47db5d33996e +size 770725 diff --git a/lib/search/indexes/github-docs-3.5-pt.json.br b/lib/search/indexes/github-docs-3.5-pt.json.br index 2e152aa64d..aa3c67de73 100644 --- a/lib/search/indexes/github-docs-3.5-pt.json.br +++ b/lib/search/indexes/github-docs-3.5-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8edbd543a76775a490f57280a16ab6bb163ccf53c7f8e0750e97c6618f0da0d1 -size 3246575 +oid sha256:4ce8c6c05dc7bad893009ba9e5d47a42afe1be4428c1b63599e844838ba18bd9 +size 3247283 diff --git a/lib/search/indexes/github-docs-3.6-cn-records.json.br b/lib/search/indexes/github-docs-3.6-cn-records.json.br index cf74ca6998..97834c3257 100644 --- a/lib/search/indexes/github-docs-3.6-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.6-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7069890407e191ef61162ac7aa72b69eaab2d834165017c70fceeced8c2c0156 -size 874339 +oid sha256:02df8748896264e5d2f2e153dfcf765a26e03d5badd5fd4b7dbb014c2b4225da +size 874346 diff --git a/lib/search/indexes/github-docs-3.6-cn.json.br b/lib/search/indexes/github-docs-3.6-cn.json.br index 5d76b4cefa..6f89d021f3 100644 --- a/lib/search/indexes/github-docs-3.6-cn.json.br +++ b/lib/search/indexes/github-docs-3.6-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7af904f4b6fbe431a6c703eb79be47a6112ec1efdf3faa0c0ebd2701c51a90e2 -size 1807589 +oid sha256:7a4b402bb56dd5737e6c714275a8d1a5b4ab47c94647d3a51c60561f7e39d858 +size 1808082 diff --git a/lib/search/indexes/github-docs-3.6-en-records.json.br b/lib/search/indexes/github-docs-3.6-en-records.json.br index a27c2aa4bb..4e45ba99f2 100644 --- a/lib/search/indexes/github-docs-3.6-en-records.json.br +++ b/lib/search/indexes/github-docs-3.6-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bc83caa795c42e78d38085cd5f6667cc6da56eb752eb2473765f6dbc1b87a8e4 -size 1202567 +oid sha256:551f7dc3ad9e5ee6d5e95a190e18daed9fe7bad91ceaebffd46d037c1a5931ba +size 1202758 diff --git a/lib/search/indexes/github-docs-3.6-en.json.br b/lib/search/indexes/github-docs-3.6-en.json.br index c0c716d098..122cd47d8d 100644 --- a/lib/search/indexes/github-docs-3.6-en.json.br +++ b/lib/search/indexes/github-docs-3.6-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:eb243d78cfebfe8d8e52595fa32b4c61c2e39c444f5e63e096f88ba7f0301f91 -size 4852373 +oid sha256:e5b53569bb4d61eea110b3abbadf719f5c2366c7cad243416810ebea0f4ce4dd +size 4852895 diff --git a/lib/search/indexes/github-docs-3.6-es-records.json.br b/lib/search/indexes/github-docs-3.6-es-records.json.br index 7fd5bc0645..af99dadbe3 100644 --- a/lib/search/indexes/github-docs-3.6-es-records.json.br +++ b/lib/search/indexes/github-docs-3.6-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:63ab8f3be141c78ab30c615813f522be6a95b5b8df1d364a3f12d26fd9c5ed26 -size 803062 +oid sha256:6618cd81a3973e8925da0ee43179b87419aa52cff63f48cb4e6f591350579e69 +size 802620 diff --git a/lib/search/indexes/github-docs-3.6-es.json.br b/lib/search/indexes/github-docs-3.6-es.json.br index 2f4573a9f3..edac60acdc 100644 --- a/lib/search/indexes/github-docs-3.6-es.json.br +++ b/lib/search/indexes/github-docs-3.6-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a02eb794157c3b345c0eddad44dc189b4f3d32bcea52a241111a0cad6aa60b09 -size 3451472 +oid sha256:cd616f5f18cd389dc9b385b9e253e23fe1ecec3b49dd4d98f02442739a1b19df +size 3445012 diff --git a/lib/search/indexes/github-docs-3.6-ja-records.json.br b/lib/search/indexes/github-docs-3.6-ja-records.json.br index b829483beb..d554a4edcf 100644 --- a/lib/search/indexes/github-docs-3.6-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.6-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3401701f18cf295316463905afdcb706f93d6ec0bf9d5c7f06e24f4c89b4afdb -size 887333 +oid sha256:6791d8e7b064d6a4b0f8d912395085988d4e0e946d92047fb21688e61a1dbdf5 +size 886442 diff --git a/lib/search/indexes/github-docs-3.6-ja.json.br b/lib/search/indexes/github-docs-3.6-ja.json.br index a179bb33e1..e47e88786e 100644 --- a/lib/search/indexes/github-docs-3.6-ja.json.br +++ b/lib/search/indexes/github-docs-3.6-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9a86436348af4af5861bbd7780f11b445d57bd66eb61196b1ea8933fb338964f -size 4914478 +oid sha256:e1c78207131ff998ea4f001f2c22d8deca237a47bc39c983fa09448d959e80f8 +size 4911981 diff --git a/lib/search/indexes/github-docs-3.6-pt-records.json.br b/lib/search/indexes/github-docs-3.6-pt-records.json.br index b9af80cdd0..0a9bde7eaf 100644 --- a/lib/search/indexes/github-docs-3.6-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.6-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1a200c213206a1969929c7799ee929cb4635cc3e31295f2734d0163f9dd7c694 -size 791409 +oid sha256:698eebddc0ee21020b51b727be182470b58373b6bff416e2d7d1a92e54a3f784 +size 791360 diff --git a/lib/search/indexes/github-docs-3.6-pt.json.br b/lib/search/indexes/github-docs-3.6-pt.json.br index 516ee9e47a..be30753f22 100644 --- a/lib/search/indexes/github-docs-3.6-pt.json.br +++ b/lib/search/indexes/github-docs-3.6-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:86580388bab174c5ed558c7ee0bd7f389fc73eb16a0c440b833117fc64519693 -size 3343809 +oid sha256:1d74466edb0803630213887f066a8c0f4f9589c33dd70aa6a6e5319fe2cc60dd +size 3343094 diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br index 37f4b8efc5..6bc7f46161 100644 --- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2cbaf2e644856e74da346bc4eb179bdc2cca720e29feed74bf907bfcfb66b5ab -size 1036207 +oid sha256:e3c6cbc41b3b5a2d40b2be8d922836e0d19aa6ab09913136131aae6eb75b995a +size 1035813 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index f7f6a0aa53..402d1b72dd 100644 --- a/lib/search/indexes/github-docs-dotcom-cn.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3418fbdb1d39e6f3fcae891308640d298a2c44312ee9fabcade4f6a3f01a8467 -size 1841510 +oid sha256:d26807291bdbb222b5106b9951bcb39eac098c71df3e5eefa7227a9c9fb453f3 +size 1844679 diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br index 9d9a49d465..8003a62a08 100644 --- a/lib/search/indexes/github-docs-dotcom-en-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6a977b70f80882546ebba5eeec9bf22a074a51dcfda137e271608edf44d0853e -size 1445163 +oid sha256:ce2ede8a8c79bee71bc9ac5846b455358e9cec397749e9d4dfe47931fc226600 +size 1445040 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index 6b44c5e2d1..f258ec93dd 100644 --- a/lib/search/indexes/github-docs-dotcom-en.json.br +++ b/lib/search/indexes/github-docs-dotcom-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:58f39cbc6e90f04602b41a1710c56d7ea381b9705755aa0cdb6243f1238c54fd -size 5566225 +oid sha256:83051ba2d0b921ed6edcf606d019ba9a595c24248b0c1903c2e2cd044ec113b0 +size 5566252 diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br index f568175d59..8638e37f32 100644 --- a/lib/search/indexes/github-docs-dotcom-es-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b7bb9db5ba3d4e6999aef5e232216a64b0398043a481de02bfa49d24624e8811 -size 934250 +oid sha256:c5ee38286761971b2cb8429e104f1173658aa406091810c609d61a3915df0a8b +size 933922 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index c99e8bae14..e7b4f9edda 100644 --- a/lib/search/indexes/github-docs-dotcom-es.json.br +++ b/lib/search/indexes/github-docs-dotcom-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:66934092b477f5a62a98c59ea2f505ea02ee15ad7d97d07e6c5ddfdc1faefdab -size 3885445 +oid sha256:340f8ff8f4944121fa5c62f30778fd4047d3d4d375d77407d410da95b16c2b1d +size 3876315 diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br index 233cf3847c..08c5d2c551 100644 --- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4ce56531d08b584248c608f499b05b21f5f7d21b4e464cd09094da013455a614 -size 1043240 +oid sha256:0b88833cc4379a8def5e69d4fcc7ef4273aaae73a349f6f4bdfedb2457ed4f41 +size 1042491 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index a32d78bd4a..9fd44971d7 100644 --- a/lib/search/indexes/github-docs-dotcom-ja.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fbfb7498a01ff65bc46ad3d47991bb2784227bf0e32eaebffab6eb218289830c -size 5607983 +oid sha256:99ecfd971ed3bfc02755878b29d400e4accb4be2622961bf4e6a8731b5e12e27 +size 5603367 diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br index d26400bf10..889073cc38 100644 --- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a064a299445ced84011f8422b86e65cb250e7996936298b2bd0991509b3f3b2a -size 923257 +oid sha256:d37d5b9715a8d4a1f1e8e975aac89db700fe003d23e4e9dd488412f97923ef3b +size 923155 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index 64067ed6c8..a0324dd733 100644 --- a/lib/search/indexes/github-docs-dotcom-pt.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f679752b629f3dfcc70d5d4bbe5a4efe5f2f75878e23363e7dd36666263494b0 -size 3800651 +oid sha256:b064eb740771a6e41d46fc75ed918208d0ae919a568f1547a9aea1a9f89574da +size 3801062 diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br index 158ee256cd..6c12475d15 100644 --- a/lib/search/indexes/github-docs-ghae-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8eb2cce701ede42f418a425d237162dfd44e7c3488a9fe7762c9e5088d75c176 -size 659180 +oid sha256:a1bc2d53e87ee58967dcd335730fe3776b18de93282fdd803df97c183442267b +size 659255 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index 3a2e83a969..2e69fd17f5 100644 --- a/lib/search/indexes/github-docs-ghae-cn.json.br +++ b/lib/search/indexes/github-docs-ghae-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fe8f0cfeef91a813c13a27c8196a6c1007caf9390a79e24a901047cc2c889a1f -size 1311026 +oid sha256:199082bef623e98b99f03f5fb1e377fa0b69797004f1687ef583486ab00d1926 +size 1310978 diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br index da50bf3ef9..74b66ba373 100644 --- a/lib/search/indexes/github-docs-ghae-en-records.json.br +++ b/lib/search/indexes/github-docs-ghae-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d58cb6e774244892146d7e2bb0b3221775f9d4ae77fcbaab96a9c4b380d2a235 -size 932648 +oid sha256:d756e0f36f3a135755c9fd8de690756d3dae4265580b11dfb0f658b7e8088380 +size 932574 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index 76157149f1..1b5f906eee 100644 --- a/lib/search/indexes/github-docs-ghae-en.json.br +++ b/lib/search/indexes/github-docs-ghae-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6fc36b7e4d3fbc64c5398d8ca938673feacd3a48f71b22c9702ecab63abc9838 -size 3697983 +oid sha256:a37455c30bb0f010e5410a54d4648f614d5f859b82ec47b55022ac9fd660889d +size 3697318 diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br index 985fe79558..790cb0a721 100644 --- a/lib/search/indexes/github-docs-ghae-es-records.json.br +++ b/lib/search/indexes/github-docs-ghae-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fb9a3b214dd83130b4df85d295b521440f74ec423e63934c06530d9fa532ef82 -size 613165 +oid sha256:510dab4bd61b63d7299835d7b2639c593fe6488d6e4c425b2f87b262af11f303 +size 613038 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index 2d5f6e0281..d7dbf71b3f 100644 --- a/lib/search/indexes/github-docs-ghae-es.json.br +++ b/lib/search/indexes/github-docs-ghae-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:95912386cad690660058938dc06b95f744a54b8158dafa7bc0b9907a67da1c00 -size 2536518 +oid sha256:0ecc811aa44b0432a17b191db2123d84f3f9e67de61dd1c1900173f4d49d3e58 +size 2531659 diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br index 9e46671367..f09904268c 100644 --- a/lib/search/indexes/github-docs-ghae-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:585592d859f874abcafcb97cd76a12a4979d9672653589bca0637b0e19f6ce8c -size 673320 +oid sha256:e4867d2dfcfa149664f226173f981c82ad75f1ae06ebfcaf3341e178fc494a84 +size 672448 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index 47122de73a..7d7e450f52 100644 --- a/lib/search/indexes/github-docs-ghae-ja.json.br +++ b/lib/search/indexes/github-docs-ghae-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:537ddd303d8397af31b6287ac4654ec167ee29cd2d5288772fd67e6188afc8be -size 3601242 +oid sha256:bbbb167bcd3aa2bd7faee5178b3b78a7c22db4d00e559b5069bdeb7f23bd6145 +size 3597310 diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br index 42c0be3016..ad4c8af178 100644 --- a/lib/search/indexes/github-docs-ghae-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e47241b870dc126c7e8c502c12221af4e0b8a81f2b8f1853505a9ae0e3396d48 -size 604324 +oid sha256:9f74fe308171e4c9f50831f54ceba651484fc74e5866dd175c18cf86d47ce518 +size 604247 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index 37ba408c1d..555044963f 100644 --- a/lib/search/indexes/github-docs-ghae-pt.json.br +++ b/lib/search/indexes/github-docs-ghae-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0efd922709faefb52adcdf3431cd7f75105ab88a48a33a5a9f363a54db2b4cd0 -size 2433883 +oid sha256:2d32bb595473525654211cae022a5e3abb05182d486f17ef19bf58df7e3bbc24 +size 2434321 diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br index 98b36f9223..ee9e309a62 100644 --- a/lib/search/indexes/github-docs-ghec-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:82fc6b0349b75548f087979b3f97ff0b289f73303f028c39918c0dc6f133d5e1 -size 1005303 +oid sha256:70d9702c005fa4eb65ada7f70ad2358bd63a3141bd28e0c1cc2783b4a3ddcdc7 +size 1005982 diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br index e40c3297be..cd2a2f6380 100644 --- a/lib/search/indexes/github-docs-ghec-cn.json.br +++ b/lib/search/indexes/github-docs-ghec-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6f139f9dd2049babcacf96bd861f6e39ebb25df68e94cd87fb97ed1754e4f0bc -size 1965025 +oid sha256:f8d6d9b19dc47342f96ce9e5a9c6545948bcd7e51e7bb3b6134e5538ceecadeb +size 1970418 diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br index ce099bd4fa..8f4cc16bfe 100644 --- a/lib/search/indexes/github-docs-ghec-en-records.json.br +++ b/lib/search/indexes/github-docs-ghec-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:28f9028dee9a6f07591e668408d97046c71e1a681ab0a8d163d806a7cc346f9d -size 1371784 +oid sha256:14063fd3f73e1a462b425ef6784a1527469ac7113ecb00b1f91f2633fcf75397 +size 1371450 diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br index c26abc156b..249007af87 100644 --- a/lib/search/indexes/github-docs-ghec-en.json.br +++ b/lib/search/indexes/github-docs-ghec-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c8dd38875cc2b1ba0796901891e114360778e35f2c30894b12ee70af7b71a6ae -size 5568340 +oid sha256:3400eda1b08c535abd2bbb0de9f95063d41dc5e7a19b2582f75586425f7ddd6d +size 5571889 diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br index 34541022fc..3633dedb7e 100644 --- a/lib/search/indexes/github-docs-ghec-es-records.json.br +++ b/lib/search/indexes/github-docs-ghec-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b51f95e2d8293d7add9eaae58a2df16bb8e436bf9dbf748006d8fa93b04725da -size 930767 +oid sha256:5c27efb96c39f6f218cd86d948233bacddbb6c56445c3420c0255a3f93627163 +size 930493 diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br index cb8671cf02..055c56d94f 100644 --- a/lib/search/indexes/github-docs-ghec-es.json.br +++ b/lib/search/indexes/github-docs-ghec-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2a9e98e71276f4a5cef6abde1a89aedf1082e5477b1495896f21180c2307aa16 -size 4018689 +oid sha256:be626feea4a82568c7465782e527f6c6ed9ff183584d9e9125f0a9fafe156b9a +size 4012135 diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br index 1eab1e6036..92e416d3a1 100644 --- a/lib/search/indexes/github-docs-ghec-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:339c0d63a401f0d6ce3470585e0ace8e4c52157a688849ba4e2d9a91b7bb7c46 -size 1018356 +oid sha256:c08d5b20e952fff5cbd36019cfb61eeeb9dfa994f1685ed4b99ad992de334b37 +size 1017980 diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br index 3ce41d1745..6c55ffa215 100644 --- a/lib/search/indexes/github-docs-ghec-ja.json.br +++ b/lib/search/indexes/github-docs-ghec-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d09d8e0d6931fb61585e1977d03e87321ef5374f4e3e1a561258600dc36ef7cd -size 5689440 +oid sha256:7c5f7e3148b4382636a8d6f82521d9da5cfaa57247d0ddff982d791471968602 +size 5686691 diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br index e7fb70052f..89e13832b3 100644 --- a/lib/search/indexes/github-docs-ghec-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:23d8e2d6dee457a8be4e12d840daecee51f39e155daa79ff958eddcef94369a8 -size 918619 +oid sha256:c930eec107be54cc5bcfd0981695f79cbe30ef09082dca1191f8d62441ea8b49 +size 918818 diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br index d6373b17d1..5ff03f28eb 100644 --- a/lib/search/indexes/github-docs-ghec-pt.json.br +++ b/lib/search/indexes/github-docs-ghec-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:49f02b6d8f76edc65c796577a66b43abd03182a4d6a24dda5413504a32bc0f37 -size 3915819 +oid sha256:cee307201c746697c2aca5b6d5ea3058d646df77096901a0204ee528419ca79f +size 3919674 diff --git a/middleware/api/session.js b/middleware/api/session.js index 4fe5d86f5c..057b69c545 100644 --- a/middleware/api/session.js +++ b/middleware/api/session.js @@ -9,7 +9,6 @@ router.get('/', (req, res) => { res.json({ isSignedIn: Boolean(req.cookies?.dotcom_user), csrfToken: req.csrfToken?.() || '', - userLanguage: req.userLanguage, }) }) diff --git a/middleware/detect-language.js b/middleware/detect-language.js index faf718f474..291676df31 100644 --- a/middleware/detect-language.js +++ b/middleware/detect-language.js @@ -1,11 +1,9 @@ import languages, { languageKeys } from '../lib/languages.js' import parser from 'accept-language-parser' -const chineseRegions = ['CN', 'HK'] +import { PREFERRED_LOCALE_COOKIE_NAME } from '../lib/constants.js' -// This value is replicated in two places! See component. -// Note, the only reason this is exported is to benefit the tests. -export const PREFERRED_LOCALE_COOKIE_NAME = 'preferredlang' +const chineseRegions = ['CN', 'HK'] function translationExists(language) { if (language.code === 'zh') { diff --git a/middleware/fast-root-redirect.js b/middleware/fast-root-redirect.js index a699011119..8545ca281a 100644 --- a/middleware/fast-root-redirect.js +++ b/middleware/fast-root-redirect.js @@ -1,5 +1,6 @@ import { cacheControlFactory } from './cache-control.js' -import { PREFERRED_LOCALE_COOKIE_NAME, getLanguageCodeFromHeader } from './detect-language.js' +import { getLanguageCodeFromHeader } from './detect-language.js' +import { PREFERRED_LOCALE_COOKIE_NAME } from '../lib/constants.js' const cacheControl = cacheControlFactory(0) diff --git a/middleware/featured-links.js b/middleware/featured-links.js index 2b34d66427..73f0ddcc18 100644 --- a/middleware/featured-links.js +++ b/middleware/featured-links.js @@ -1,4 +1,5 @@ import getLinkData from '../lib/get-link-data.js' +import renderContent from '../lib/render-content/index.js' // this middleware adds properties to the context object export default async function featuredLinks(req, res, next) { @@ -19,7 +20,22 @@ export default async function featuredLinks(req, res, next) { if (key === 'videos') { // Videos are external URLs so don't run through getLinkData, they're // objects with title and href properties. - req.context.featuredLinks[key] = req.context.page.featuredLinks[key] + // When the title contains Liquid versioning tags, it will be either + // the provided string title or an empty title. When the title is empty, + // it indicates the video is not versioned for the current version + req.context.featuredLinks[key] = [] + for (let i = 0; i < req.context.page.featuredLinks[key].length; i++) { + const title = await renderContent( + req.context.page.featuredLinks[key][i].title, + req.context, + { + textOnly: true, + encodeEntities: true, + } + ) + const item = { title, href: req.context.page.featuredLinks[key][i].href } + req.context.featuredLinks[key].push(item) + } } else { req.context.featuredLinks[key] = await getLinkData( req.context.page.featuredLinks[key], diff --git a/package-lock.json b/package-lock.json index 46002fd01f..dae40a174b 100644 --- a/package-lock.json +++ b/package-lock.json @@ -109,8 +109,8 @@ "@types/react-dom": "^18.0.5", "@types/react-syntax-highlighter": "^15.5.2", "@types/uuid": "^8.3.4", - "@typescript-eslint/eslint-plugin": "5.30.7", - "@typescript-eslint/parser": "5.30.7", + "@typescript-eslint/eslint-plugin": "5.33.0", + "@typescript-eslint/parser": "5.33.0", "babel-loader": "^8.2.5", "babel-plugin-styled-components": "^2.0.7", "babel-preset-env": "^1.7.0", @@ -121,7 +121,7 @@ "csp-parse": "0.0.2", "dedent": "^0.7.0", "domwaiter": "^1.3.0", - "eslint": "8.20.0", + "eslint": "8.21.0", "eslint-config-prettier": "^8.5.0", "eslint-config-standard": "^17.0.0", "eslint-plugin-import": "^2.26.0", @@ -2195,9 +2195,10 @@ } }, "node_modules/@humanwhocodes/config-array": { - "version": "0.9.5", + "version": "0.10.4", + "resolved": "https://registry.npmjs.org/@humanwhocodes/config-array/-/config-array-0.10.4.tgz", + "integrity": "sha512-mXAIHxZT3Vcpg83opl1wGlVZ9xydbfZO3r5YfRSH6Gpp2J/PfdBP0wbDa2sO6/qRbcalpoevVyW6A/fI6LfeMw==", "dev": true, - "license": "Apache-2.0", "dependencies": { "@humanwhocodes/object-schema": "^1.2.1", "debug": "^4.1.1", @@ -2209,8 +2210,9 @@ }, "node_modules/@humanwhocodes/config-array/node_modules/brace-expansion": { "version": "1.1.11", + "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz", + "integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==", "dev": true, - "license": "MIT", "dependencies": { "balanced-match": "^1.0.0", "concat-map": "0.0.1" @@ -2218,8 +2220,9 @@ }, "node_modules/@humanwhocodes/config-array/node_modules/minimatch": { "version": "3.1.2", + "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz", + "integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==", "dev": true, - "license": "ISC", "dependencies": { "brace-expansion": "^1.1.7" }, @@ -2227,10 +2230,21 @@ "node": "*" } }, + "node_modules/@humanwhocodes/gitignore-to-minimatch": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/@humanwhocodes/gitignore-to-minimatch/-/gitignore-to-minimatch-1.0.2.tgz", + "integrity": "sha512-rSqmMJDdLFUsyxR6FMtD00nfQKKLFb1kv+qBbOVKqErvloEIJLo5bDTJTQNTYgeyp78JsA7u/NPi5jT1GR/MuA==", + "dev": true, + "funding": { + "type": "github", + "url": "https://github.com/sponsors/nzakas" + } + }, "node_modules/@humanwhocodes/object-schema": { "version": "1.2.1", - "dev": true, - "license": "BSD-3-Clause" + "resolved": "https://registry.npmjs.org/@humanwhocodes/object-schema/-/object-schema-1.2.1.tgz", + "integrity": "sha512-ZnQMnLV4e7hDlUvw8H+U8ASL02SS2Gn6+9Ac3wGGLIe7+je2AeAOxPY+izIPJDfFDb7eDjev0Us8MO1iFRN8hA==", + "dev": true }, "node_modules/@istanbuljs/load-nyc-config": { "version": "1.1.0", @@ -4418,14 +4432,14 @@ } }, "node_modules/@typescript-eslint/eslint-plugin": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/eslint-plugin/-/eslint-plugin-5.30.7.tgz", - "integrity": "sha512-l4L6Do+tfeM2OK0GJsU7TUcM/1oN/N25xHm3Jb4z3OiDU4Lj8dIuxX9LpVMS9riSXQs42D1ieX7b85/r16H9Fw==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/eslint-plugin/-/eslint-plugin-5.33.0.tgz", + "integrity": "sha512-jHvZNSW2WZ31OPJ3enhLrEKvAZNyAFWZ6rx9tUwaessTc4sx9KmgMNhVcqVAl1ETnT5rU5fpXTLmY9YvC1DCNg==", "dev": true, "dependencies": { - "@typescript-eslint/scope-manager": "5.30.7", - "@typescript-eslint/type-utils": "5.30.7", - "@typescript-eslint/utils": "5.30.7", + "@typescript-eslint/scope-manager": "5.33.0", + "@typescript-eslint/type-utils": "5.33.0", + "@typescript-eslint/utils": "5.33.0", "debug": "^4.3.4", "functional-red-black-tree": "^1.0.1", "ignore": "^5.2.0", @@ -4468,14 +4482,14 @@ } }, "node_modules/@typescript-eslint/parser": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/parser/-/parser-5.30.7.tgz", - "integrity": "sha512-Rg5xwznHWWSy7v2o0cdho6n+xLhK2gntImp0rJroVVFkcYFYQ8C8UJTSuTw/3CnExBmPjycjmUJkxVmjXsld6A==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/parser/-/parser-5.33.0.tgz", + "integrity": "sha512-cgM5cJrWmrDV2KpvlcSkelTBASAs1mgqq+IUGKJvFxWrapHpaRy5EXPQz9YaKF3nZ8KY18ILTiVpUtbIac86/w==", "dev": true, "dependencies": { - "@typescript-eslint/scope-manager": "5.30.7", - "@typescript-eslint/types": "5.30.7", - "@typescript-eslint/typescript-estree": "5.30.7", + "@typescript-eslint/scope-manager": "5.33.0", + "@typescript-eslint/types": "5.33.0", + "@typescript-eslint/typescript-estree": "5.33.0", "debug": "^4.3.4" }, "engines": { @@ -4512,13 +4526,13 @@ } }, "node_modules/@typescript-eslint/scope-manager": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/scope-manager/-/scope-manager-5.30.7.tgz", - "integrity": "sha512-7BM1bwvdF1UUvt+b9smhqdc/eniOnCKxQT/kj3oXtj3LqnTWCAM0qHRHfyzCzhEfWX0zrW7KqXXeE4DlchZBKw==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/scope-manager/-/scope-manager-5.33.0.tgz", + "integrity": "sha512-/Jta8yMNpXYpRDl8EwF/M8It2A9sFJTubDo0ATZefGXmOqlaBffEw0ZbkbQ7TNDK6q55NPHFshGBPAZvZkE8Pw==", "dev": true, "dependencies": { - "@typescript-eslint/types": "5.30.7", - "@typescript-eslint/visitor-keys": "5.30.7" + "@typescript-eslint/types": "5.33.0", + "@typescript-eslint/visitor-keys": "5.33.0" }, "engines": { "node": "^12.22.0 || ^14.17.0 || >=16.0.0" @@ -4529,12 +4543,12 @@ } }, "node_modules/@typescript-eslint/type-utils": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/type-utils/-/type-utils-5.30.7.tgz", - "integrity": "sha512-nD5qAE2aJX/YLyKMvOU5jvJyku4QN5XBVsoTynFrjQZaDgDV6i7QHFiYCx10wvn7hFvfuqIRNBtsgaLe0DbWhw==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/type-utils/-/type-utils-5.33.0.tgz", + "integrity": "sha512-2zB8uEn7hEH2pBeyk3NpzX1p3lF9dKrEbnXq1F7YkpZ6hlyqb2yZujqgRGqXgRBTHWIUG3NGx/WeZk224UKlIA==", "dev": true, "dependencies": { - "@typescript-eslint/utils": "5.30.7", + "@typescript-eslint/utils": "5.33.0", "debug": "^4.3.4", "tsutils": "^3.21.0" }, @@ -4572,9 +4586,9 @@ } }, "node_modules/@typescript-eslint/types": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/types/-/types-5.30.7.tgz", - "integrity": "sha512-ocVkETUs82+U+HowkovV6uxf1AnVRKCmDRNUBUUo46/5SQv1owC/EBFkiu4MOHeZqhKz2ktZ3kvJJ1uFqQ8QPg==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/types/-/types-5.33.0.tgz", + "integrity": "sha512-nIMt96JngB4MYFYXpZ/3ZNU4GWPNdBbcB5w2rDOCpXOVUkhtNlG2mmm8uXhubhidRZdwMaMBap7Uk8SZMU/ppw==", "dev": true, "engines": { "node": "^12.22.0 || ^14.17.0 || >=16.0.0" @@ -4585,13 +4599,13 @@ } }, "node_modules/@typescript-eslint/typescript-estree": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/typescript-estree/-/typescript-estree-5.30.7.tgz", - "integrity": "sha512-tNslqXI1ZdmXXrHER83TJ8OTYl4epUzJC0aj2i4DMDT4iU+UqLT3EJeGQvJ17BMbm31x5scSwo3hPM0nqQ1AEA==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/typescript-estree/-/typescript-estree-5.33.0.tgz", + "integrity": "sha512-tqq3MRLlggkJKJUrzM6wltk8NckKyyorCSGMq4eVkyL5sDYzJJcMgZATqmF8fLdsWrW7OjjIZ1m9v81vKcaqwQ==", "dev": true, "dependencies": { - "@typescript-eslint/types": "5.30.7", - "@typescript-eslint/visitor-keys": "5.30.7", + "@typescript-eslint/types": "5.33.0", + "@typescript-eslint/visitor-keys": "5.33.0", "debug": "^4.3.4", "globby": "^11.1.0", "is-glob": "^4.0.3", @@ -4629,15 +4643,15 @@ } }, "node_modules/@typescript-eslint/utils": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/utils/-/utils-5.30.7.tgz", - "integrity": "sha512-Z3pHdbFw+ftZiGUnm1GZhkJgVqsDL5CYW2yj+TB2mfXDFOMqtbzQi2dNJIyPqPbx9mv2kUxS1gU+r2gKlKi1rQ==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/utils/-/utils-5.33.0.tgz", + "integrity": "sha512-JxOAnXt9oZjXLIiXb5ZIcZXiwVHCkqZgof0O8KPgz7C7y0HS42gi75PdPlqh1Tf109M0fyUw45Ao6JLo7S5AHw==", "dev": true, "dependencies": { "@types/json-schema": "^7.0.9", - "@typescript-eslint/scope-manager": "5.30.7", - "@typescript-eslint/types": "5.30.7", - "@typescript-eslint/typescript-estree": "5.30.7", + "@typescript-eslint/scope-manager": "5.33.0", + "@typescript-eslint/types": "5.33.0", + "@typescript-eslint/typescript-estree": "5.33.0", "eslint-scope": "^5.1.1", "eslint-utils": "^3.0.0" }, @@ -4671,12 +4685,12 @@ } }, "node_modules/@typescript-eslint/visitor-keys": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/visitor-keys/-/visitor-keys-5.30.7.tgz", - "integrity": "sha512-KrRXf8nnjvcpxDFOKej4xkD7657+PClJs5cJVSG7NNoCNnjEdc46juNAQt7AyuWctuCgs6mVRc1xGctEqrjxWw==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/visitor-keys/-/visitor-keys-5.33.0.tgz", + "integrity": "sha512-/XsqCzD4t+Y9p5wd9HZiptuGKBlaZO5showwqODii5C0nZawxWLF+Q6k5wYHBrQv96h6GYKyqqMHCSTqta8Kiw==", "dev": true, "dependencies": { - "@typescript-eslint/types": "5.30.7", + "@typescript-eslint/types": "5.33.0", "eslint-visitor-keys": "^3.3.0" }, "engines": { @@ -4905,9 +4919,9 @@ } }, "node_modules/acorn": { - "version": "8.7.1", - "resolved": "https://registry.npmjs.org/acorn/-/acorn-8.7.1.tgz", - "integrity": "sha512-Xx54uLJQZ19lKygFXOWsscKUbsBZW0CPykPhVQdhIeIwrbPmJzqeASDInc8nKBnp/JT6igTs82qPXz069H8I/A==", + "version": "8.8.0", + "resolved": "https://registry.npmjs.org/acorn/-/acorn-8.8.0.tgz", + "integrity": "sha512-QOxyigPVrpZ2GXT+PFyZTl6TtOFc5egxHIP9IlQ+RbupQuX4RkT/Bee4/kQuC02Xkzg84JcT7oLYtDIQxp+v7w==", "dev": true, "bin": { "acorn": "bin/acorn" @@ -7851,13 +7865,14 @@ } }, "node_modules/eslint": { - "version": "8.20.0", - "resolved": "https://registry.npmjs.org/eslint/-/eslint-8.20.0.tgz", - "integrity": "sha512-d4ixhz5SKCa1D6SCPrivP7yYVi7nyD6A4vs6HIAul9ujBzcEmZVM3/0NN/yu5nKhmO1wjp5xQ46iRfmDGlOviA==", + "version": "8.21.0", + "resolved": "https://registry.npmjs.org/eslint/-/eslint-8.21.0.tgz", + "integrity": "sha512-/XJ1+Qurf1T9G2M5IHrsjp+xrGT73RZf23xA1z5wB1ZzzEAWSZKvRwhWxTFp1rvkvCfwcvAUNAP31bhKTTGfDA==", "dev": true, "dependencies": { "@eslint/eslintrc": "^1.3.0", - "@humanwhocodes/config-array": "^0.9.2", + "@humanwhocodes/config-array": "^0.10.4", + "@humanwhocodes/gitignore-to-minimatch": "^1.0.2", "ajv": "^6.10.0", "chalk": "^4.0.0", "cross-spawn": "^7.0.2", @@ -7867,14 +7882,17 @@ "eslint-scope": "^7.1.1", "eslint-utils": "^3.0.0", "eslint-visitor-keys": "^3.3.0", - "espree": "^9.3.2", + "espree": "^9.3.3", "esquery": "^1.4.0", "esutils": "^2.0.2", "fast-deep-equal": "^3.1.3", "file-entry-cache": "^6.0.1", + "find-up": "^5.0.0", "functional-red-black-tree": "^1.0.1", "glob-parent": "^6.0.1", "globals": "^13.15.0", + "globby": "^11.1.0", + "grapheme-splitter": "^1.0.4", "ignore": "^5.2.0", "import-fresh": "^3.0.0", "imurmurhash": "^0.1.4", @@ -8400,6 +8418,22 @@ "node": ">=4.0" } }, + "node_modules/eslint/node_modules/find-up": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/find-up/-/find-up-5.0.0.tgz", + "integrity": "sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==", + "dev": true, + "dependencies": { + "locate-path": "^6.0.0", + "path-exists": "^4.0.0" + }, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, "node_modules/eslint/node_modules/glob-parent": { "version": "6.0.2", "dev": true, @@ -8431,6 +8465,21 @@ "dev": true, "license": "MIT" }, + "node_modules/eslint/node_modules/locate-path": { + "version": "6.0.0", + "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-6.0.0.tgz", + "integrity": "sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==", + "dev": true, + "dependencies": { + "p-locate": "^5.0.0" + }, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, "node_modules/eslint/node_modules/minimatch": { "version": "3.1.2", "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz", @@ -8443,6 +8492,30 @@ "node": "*" } }, + "node_modules/eslint/node_modules/p-locate": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/p-locate/-/p-locate-5.0.0.tgz", + "integrity": "sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==", + "dev": true, + "dependencies": { + "p-limit": "^3.0.2" + }, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/eslint/node_modules/path-exists": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/path-exists/-/path-exists-4.0.0.tgz", + "integrity": "sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==", + "dev": true, + "engines": { + "node": ">=8" + } + }, "node_modules/eslint/node_modules/strip-ansi": { "version": "6.0.1", "dev": true, @@ -8476,17 +8549,20 @@ } }, "node_modules/espree": { - "version": "9.3.2", - "resolved": "https://registry.npmjs.org/espree/-/espree-9.3.2.tgz", - "integrity": "sha512-D211tC7ZwouTIuY5x9XnS0E9sWNChB7IYKX/Xp5eQj3nFXhqmiUDB9q27y76oFl8jTg3pXcQx/bpxMfs3CIZbA==", + "version": "9.3.3", + "resolved": "https://registry.npmjs.org/espree/-/espree-9.3.3.tgz", + "integrity": "sha512-ORs1Rt/uQTqUKjDdGCyrtYxbazf5umATSf/K4qxjmZHORR6HJk+2s/2Pqe+Kk49HHINC/xNIrGfgh8sZcll0ng==", "dev": true, "dependencies": { - "acorn": "^8.7.1", + "acorn": "^8.8.0", "acorn-jsx": "^5.3.2", "eslint-visitor-keys": "^3.3.0" }, "engines": { "node": "^12.22.0 || ^14.17.0 || >=16.0.0" + }, + "funding": { + "url": "https://opencollective.com/eslint" } }, "node_modules/espree/node_modules/eslint-visitor-keys": { @@ -9779,6 +9855,12 @@ "devOptional": true, "license": "ISC" }, + "node_modules/grapheme-splitter": { + "version": "1.0.4", + "resolved": "https://registry.npmjs.org/grapheme-splitter/-/grapheme-splitter-1.0.4.tgz", + "integrity": "sha512-bzh50DW9kTPM00T8y4o8vQg89Di9oLJVLW/KaOGIXJWP/iqCN6WKYkbNOF04vFLJhwcpYUh9ydh/+5vpOqV4YQ==", + "dev": true + }, "node_modules/graphql": { "version": "16.5.0", "resolved": "https://registry.npmjs.org/graphql/-/graphql-16.5.0.tgz", @@ -22172,7 +22254,9 @@ } }, "@humanwhocodes/config-array": { - "version": "0.9.5", + "version": "0.10.4", + "resolved": "https://registry.npmjs.org/@humanwhocodes/config-array/-/config-array-0.10.4.tgz", + "integrity": "sha512-mXAIHxZT3Vcpg83opl1wGlVZ9xydbfZO3r5YfRSH6Gpp2J/PfdBP0wbDa2sO6/qRbcalpoevVyW6A/fI6LfeMw==", "dev": true, "requires": { "@humanwhocodes/object-schema": "^1.2.1", @@ -22182,6 +22266,8 @@ "dependencies": { "brace-expansion": { "version": "1.1.11", + "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz", + "integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==", "dev": true, "requires": { "balanced-match": "^1.0.0", @@ -22190,6 +22276,8 @@ }, "minimatch": { "version": "3.1.2", + "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz", + "integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==", "dev": true, "requires": { "brace-expansion": "^1.1.7" @@ -22197,8 +22285,16 @@ } } }, + "@humanwhocodes/gitignore-to-minimatch": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/@humanwhocodes/gitignore-to-minimatch/-/gitignore-to-minimatch-1.0.2.tgz", + "integrity": "sha512-rSqmMJDdLFUsyxR6FMtD00nfQKKLFb1kv+qBbOVKqErvloEIJLo5bDTJTQNTYgeyp78JsA7u/NPi5jT1GR/MuA==", + "dev": true + }, "@humanwhocodes/object-schema": { "version": "1.2.1", + "resolved": "https://registry.npmjs.org/@humanwhocodes/object-schema/-/object-schema-1.2.1.tgz", + "integrity": "sha512-ZnQMnLV4e7hDlUvw8H+U8ASL02SS2Gn6+9Ac3wGGLIe7+je2AeAOxPY+izIPJDfFDb7eDjev0Us8MO1iFRN8hA==", "dev": true }, "@istanbuljs/load-nyc-config": { @@ -23904,14 +24000,14 @@ } }, "@typescript-eslint/eslint-plugin": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/eslint-plugin/-/eslint-plugin-5.30.7.tgz", - "integrity": "sha512-l4L6Do+tfeM2OK0GJsU7TUcM/1oN/N25xHm3Jb4z3OiDU4Lj8dIuxX9LpVMS9riSXQs42D1ieX7b85/r16H9Fw==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/eslint-plugin/-/eslint-plugin-5.33.0.tgz", + "integrity": "sha512-jHvZNSW2WZ31OPJ3enhLrEKvAZNyAFWZ6rx9tUwaessTc4sx9KmgMNhVcqVAl1ETnT5rU5fpXTLmY9YvC1DCNg==", "dev": true, "requires": { - "@typescript-eslint/scope-manager": "5.30.7", - "@typescript-eslint/type-utils": "5.30.7", - "@typescript-eslint/utils": "5.30.7", + "@typescript-eslint/scope-manager": "5.33.0", + "@typescript-eslint/type-utils": "5.33.0", + "@typescript-eslint/utils": "5.33.0", "debug": "^4.3.4", "functional-red-black-tree": "^1.0.1", "ignore": "^5.2.0", @@ -23932,14 +24028,14 @@ } }, "@typescript-eslint/parser": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/parser/-/parser-5.30.7.tgz", - "integrity": "sha512-Rg5xwznHWWSy7v2o0cdho6n+xLhK2gntImp0rJroVVFkcYFYQ8C8UJTSuTw/3CnExBmPjycjmUJkxVmjXsld6A==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/parser/-/parser-5.33.0.tgz", + "integrity": "sha512-cgM5cJrWmrDV2KpvlcSkelTBASAs1mgqq+IUGKJvFxWrapHpaRy5EXPQz9YaKF3nZ8KY18ILTiVpUtbIac86/w==", "dev": true, "requires": { - "@typescript-eslint/scope-manager": "5.30.7", - "@typescript-eslint/types": "5.30.7", - "@typescript-eslint/typescript-estree": "5.30.7", + "@typescript-eslint/scope-manager": "5.33.0", + "@typescript-eslint/types": "5.33.0", + "@typescript-eslint/typescript-estree": "5.33.0", "debug": "^4.3.4" }, "dependencies": { @@ -23955,22 +24051,22 @@ } }, "@typescript-eslint/scope-manager": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/scope-manager/-/scope-manager-5.30.7.tgz", - "integrity": "sha512-7BM1bwvdF1UUvt+b9smhqdc/eniOnCKxQT/kj3oXtj3LqnTWCAM0qHRHfyzCzhEfWX0zrW7KqXXeE4DlchZBKw==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/scope-manager/-/scope-manager-5.33.0.tgz", + "integrity": "sha512-/Jta8yMNpXYpRDl8EwF/M8It2A9sFJTubDo0ATZefGXmOqlaBffEw0ZbkbQ7TNDK6q55NPHFshGBPAZvZkE8Pw==", "dev": true, "requires": { - "@typescript-eslint/types": "5.30.7", - "@typescript-eslint/visitor-keys": "5.30.7" + "@typescript-eslint/types": "5.33.0", + "@typescript-eslint/visitor-keys": "5.33.0" } }, "@typescript-eslint/type-utils": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/type-utils/-/type-utils-5.30.7.tgz", - "integrity": "sha512-nD5qAE2aJX/YLyKMvOU5jvJyku4QN5XBVsoTynFrjQZaDgDV6i7QHFiYCx10wvn7hFvfuqIRNBtsgaLe0DbWhw==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/type-utils/-/type-utils-5.33.0.tgz", + "integrity": "sha512-2zB8uEn7hEH2pBeyk3NpzX1p3lF9dKrEbnXq1F7YkpZ6hlyqb2yZujqgRGqXgRBTHWIUG3NGx/WeZk224UKlIA==", "dev": true, "requires": { - "@typescript-eslint/utils": "5.30.7", + "@typescript-eslint/utils": "5.33.0", "debug": "^4.3.4", "tsutils": "^3.21.0" }, @@ -23987,19 +24083,19 @@ } }, "@typescript-eslint/types": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/types/-/types-5.30.7.tgz", - "integrity": "sha512-ocVkETUs82+U+HowkovV6uxf1AnVRKCmDRNUBUUo46/5SQv1owC/EBFkiu4MOHeZqhKz2ktZ3kvJJ1uFqQ8QPg==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/types/-/types-5.33.0.tgz", + "integrity": "sha512-nIMt96JngB4MYFYXpZ/3ZNU4GWPNdBbcB5w2rDOCpXOVUkhtNlG2mmm8uXhubhidRZdwMaMBap7Uk8SZMU/ppw==", "dev": true }, "@typescript-eslint/typescript-estree": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/typescript-estree/-/typescript-estree-5.30.7.tgz", - "integrity": "sha512-tNslqXI1ZdmXXrHER83TJ8OTYl4epUzJC0aj2i4DMDT4iU+UqLT3EJeGQvJ17BMbm31x5scSwo3hPM0nqQ1AEA==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/typescript-estree/-/typescript-estree-5.33.0.tgz", + "integrity": "sha512-tqq3MRLlggkJKJUrzM6wltk8NckKyyorCSGMq4eVkyL5sDYzJJcMgZATqmF8fLdsWrW7OjjIZ1m9v81vKcaqwQ==", "dev": true, "requires": { - "@typescript-eslint/types": "5.30.7", - "@typescript-eslint/visitor-keys": "5.30.7", + "@typescript-eslint/types": "5.33.0", + "@typescript-eslint/visitor-keys": "5.33.0", "debug": "^4.3.4", "globby": "^11.1.0", "is-glob": "^4.0.3", @@ -24019,15 +24115,15 @@ } }, "@typescript-eslint/utils": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/utils/-/utils-5.30.7.tgz", - "integrity": "sha512-Z3pHdbFw+ftZiGUnm1GZhkJgVqsDL5CYW2yj+TB2mfXDFOMqtbzQi2dNJIyPqPbx9mv2kUxS1gU+r2gKlKi1rQ==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/utils/-/utils-5.33.0.tgz", + "integrity": "sha512-JxOAnXt9oZjXLIiXb5ZIcZXiwVHCkqZgof0O8KPgz7C7y0HS42gi75PdPlqh1Tf109M0fyUw45Ao6JLo7S5AHw==", "dev": true, "requires": { "@types/json-schema": "^7.0.9", - "@typescript-eslint/scope-manager": "5.30.7", - "@typescript-eslint/types": "5.30.7", - "@typescript-eslint/typescript-estree": "5.30.7", + "@typescript-eslint/scope-manager": "5.33.0", + "@typescript-eslint/types": "5.33.0", + "@typescript-eslint/typescript-estree": "5.33.0", "eslint-scope": "^5.1.1", "eslint-utils": "^3.0.0" }, @@ -24044,12 +24140,12 @@ } }, "@typescript-eslint/visitor-keys": { - "version": "5.30.7", - "resolved": "https://registry.npmjs.org/@typescript-eslint/visitor-keys/-/visitor-keys-5.30.7.tgz", - "integrity": "sha512-KrRXf8nnjvcpxDFOKej4xkD7657+PClJs5cJVSG7NNoCNnjEdc46juNAQt7AyuWctuCgs6mVRc1xGctEqrjxWw==", + "version": "5.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/visitor-keys/-/visitor-keys-5.33.0.tgz", + "integrity": "sha512-/XsqCzD4t+Y9p5wd9HZiptuGKBlaZO5showwqODii5C0nZawxWLF+Q6k5wYHBrQv96h6GYKyqqMHCSTqta8Kiw==", "dev": true, "requires": { - "@typescript-eslint/types": "5.30.7", + "@typescript-eslint/types": "5.33.0", "eslint-visitor-keys": "^3.3.0" }, "dependencies": { @@ -24262,9 +24358,9 @@ } }, "acorn": { - "version": "8.7.1", - "resolved": "https://registry.npmjs.org/acorn/-/acorn-8.7.1.tgz", - "integrity": "sha512-Xx54uLJQZ19lKygFXOWsscKUbsBZW0CPykPhVQdhIeIwrbPmJzqeASDInc8nKBnp/JT6igTs82qPXz069H8I/A==", + "version": "8.8.0", + "resolved": "https://registry.npmjs.org/acorn/-/acorn-8.8.0.tgz", + "integrity": "sha512-QOxyigPVrpZ2GXT+PFyZTl6TtOFc5egxHIP9IlQ+RbupQuX4RkT/Bee4/kQuC02Xkzg84JcT7oLYtDIQxp+v7w==", "dev": true }, "acorn-import-assertions": { @@ -26330,13 +26426,14 @@ "dev": true }, "eslint": { - "version": "8.20.0", - "resolved": "https://registry.npmjs.org/eslint/-/eslint-8.20.0.tgz", - "integrity": "sha512-d4ixhz5SKCa1D6SCPrivP7yYVi7nyD6A4vs6HIAul9ujBzcEmZVM3/0NN/yu5nKhmO1wjp5xQ46iRfmDGlOviA==", + "version": "8.21.0", + "resolved": "https://registry.npmjs.org/eslint/-/eslint-8.21.0.tgz", + "integrity": "sha512-/XJ1+Qurf1T9G2M5IHrsjp+xrGT73RZf23xA1z5wB1ZzzEAWSZKvRwhWxTFp1rvkvCfwcvAUNAP31bhKTTGfDA==", "dev": true, "requires": { "@eslint/eslintrc": "^1.3.0", - "@humanwhocodes/config-array": "^0.9.2", + "@humanwhocodes/config-array": "^0.10.4", + "@humanwhocodes/gitignore-to-minimatch": "^1.0.2", "ajv": "^6.10.0", "chalk": "^4.0.0", "cross-spawn": "^7.0.2", @@ -26346,14 +26443,17 @@ "eslint-scope": "^7.1.1", "eslint-utils": "^3.0.0", "eslint-visitor-keys": "^3.3.0", - "espree": "^9.3.2", + "espree": "^9.3.3", "esquery": "^1.4.0", "esutils": "^2.0.2", "fast-deep-equal": "^3.1.3", "file-entry-cache": "^6.0.1", + "find-up": "^5.0.0", "functional-red-black-tree": "^1.0.1", "glob-parent": "^6.0.1", "globals": "^13.15.0", + "globby": "^11.1.0", + "grapheme-splitter": "^1.0.4", "ignore": "^5.2.0", "import-fresh": "^3.0.0", "imurmurhash": "^0.1.4", @@ -26429,6 +26529,16 @@ "version": "5.3.0", "dev": true }, + "find-up": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/find-up/-/find-up-5.0.0.tgz", + "integrity": "sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==", + "dev": true, + "requires": { + "locate-path": "^6.0.0", + "path-exists": "^4.0.0" + } + }, "glob-parent": { "version": "6.0.2", "dev": true, @@ -26449,6 +26559,15 @@ "version": "0.4.1", "dev": true }, + "locate-path": { + "version": "6.0.0", + "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-6.0.0.tgz", + "integrity": "sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==", + "dev": true, + "requires": { + "p-locate": "^5.0.0" + } + }, "minimatch": { "version": "3.1.2", "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz", @@ -26458,6 +26577,21 @@ "brace-expansion": "^1.1.7" } }, + "p-locate": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/p-locate/-/p-locate-5.0.0.tgz", + "integrity": "sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==", + "dev": true, + "requires": { + "p-limit": "^3.0.2" + } + }, + "path-exists": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/path-exists/-/path-exists-4.0.0.tgz", + "integrity": "sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==", + "dev": true + }, "strip-ansi": { "version": "6.0.1", "dev": true, @@ -26752,12 +26886,12 @@ "optional": true }, "espree": { - "version": "9.3.2", - "resolved": "https://registry.npmjs.org/espree/-/espree-9.3.2.tgz", - "integrity": "sha512-D211tC7ZwouTIuY5x9XnS0E9sWNChB7IYKX/Xp5eQj3nFXhqmiUDB9q27y76oFl8jTg3pXcQx/bpxMfs3CIZbA==", + "version": "9.3.3", + "resolved": "https://registry.npmjs.org/espree/-/espree-9.3.3.tgz", + "integrity": "sha512-ORs1Rt/uQTqUKjDdGCyrtYxbazf5umATSf/K4qxjmZHORR6HJk+2s/2Pqe+Kk49HHINC/xNIrGfgh8sZcll0ng==", "dev": true, "requires": { - "acorn": "^8.7.1", + "acorn": "^8.8.0", "acorn-jsx": "^5.3.2", "eslint-visitor-keys": "^3.3.0" }, @@ -27656,6 +27790,12 @@ "version": "4.2.10", "devOptional": true }, + "grapheme-splitter": { + "version": "1.0.4", + "resolved": "https://registry.npmjs.org/grapheme-splitter/-/grapheme-splitter-1.0.4.tgz", + "integrity": "sha512-bzh50DW9kTPM00T8y4o8vQg89Di9oLJVLW/KaOGIXJWP/iqCN6WKYkbNOF04vFLJhwcpYUh9ydh/+5vpOqV4YQ==", + "dev": true + }, "graphql": { "version": "16.5.0", "resolved": "https://registry.npmjs.org/graphql/-/graphql-16.5.0.tgz", diff --git a/package.json b/package.json index f620c3bd15..9dd92dada7 100644 --- a/package.json +++ b/package.json @@ -111,8 +111,8 @@ "@types/react-dom": "^18.0.5", "@types/react-syntax-highlighter": "^15.5.2", "@types/uuid": "^8.3.4", - "@typescript-eslint/eslint-plugin": "5.30.7", - "@typescript-eslint/parser": "5.30.7", + "@typescript-eslint/eslint-plugin": "5.33.0", + "@typescript-eslint/parser": "5.33.0", "babel-loader": "^8.2.5", "babel-plugin-styled-components": "^2.0.7", "babel-preset-env": "^1.7.0", @@ -123,7 +123,7 @@ "csp-parse": "0.0.2", "dedent": "^0.7.0", "domwaiter": "^1.3.0", - "eslint": "8.20.0", + "eslint": "8.21.0", "eslint-config-prettier": "^8.5.0", "eslint-config-standard": "^17.0.0", "eslint-plugin-import": "^2.26.0", diff --git a/tests/meta/repository-references.js b/tests/meta/repository-references.js index e2112204cb..35bdfbb030 100644 --- a/tests/meta/repository-references.js +++ b/tests/meta/repository-references.js @@ -17,67 +17,68 @@ If this test is failing... // These are a list of known public repositories in the GitHub organization const PUBLIC_REPOS = new Set([ - 'site-policy', - 'roadmap', - 'linguist', - 'super-linter', + 'actions-oidc-gateway-example', + 'advisory-database', 'backup-utils', + 'browser-support', + 'choosealicense.com', 'codeql-action-sync-tool', 'codeql-action', 'codeql-cli-binaries', - 'codeql', 'codeql-go', - 'platform-samples', - 'github-services', - 'explore', - 'enterprise-releases', - 'markup', - 'hubot', - 'VisualStudio', 'codeql', - 'gitignore', - 'feedback', - 'semantic', - 'git-lfs', - 'git-sizer', - 'dmca', - 'gov-takedowns', - 'janky', - 'rest-api-description', - 'smimesign', - 'tweetsodium', - 'choosealicense.com', - 'renaming', - 'localization-support', - 'docs', - 'securitylab', - 'hello-world', - 'hello-world.git', - 'insights-releases', - 'help-docs-archived-enterprise-versions', - 'stack-graphs', + 'codeql', 'codespaces-precache', - 'advisory-database', - 'browser-support', - 'haikus-for-codespaces', - 'actions-oidc-gateway-example', 'copilot.vim', 'dependency-submission-toolkit', + 'dmca', + 'docs', + 'enterprise-releases', + 'explore', + 'feedback', + 'gh-net', + 'git-lfs', + 'git-sizer', + 'github-services', + 'gitignore', + 'gov-takedowns', + 'haikus-for-codespaces', + 'hello-world.git', + 'hello-world', + 'help-docs-archived-enterprise-versions', + 'hubot', + 'insights-releases', + 'janky', + 'linguist', + 'localization-support', + 'markup', + 'platform-samples', + 'renaming', + 'rest-api-description', + 'roadmap', + 'securitylab', + 'semantic', + 'site-policy', + 'smimesign', + 'stack-graphs', + 'super-linter', + 'tweetsodium', + 'VisualStudio', ]) const ALLOW_DOCS_PATHS = [ '.github/actions-scripts/enterprise-server-issue-templates/*.md', '.github/review-template.md', + '.github/workflows/hubber-contribution-help.yml', '.github/workflows/sync-search-indices.yml', 'contributing/search.md', + 'docs/index.yaml', + 'lib/excluded-links.js', 'lib/rest/**/*.json', 'lib/webhooks/**/*.json', 'ownership.yaml', - 'docs/index.yaml', - 'lib/excluded-links.js', 'script/README.md', 'script/toggle-ghae-feature-flags.js', - '.github/workflows/hubber-contribution-help.yml', ] const REPO_REGEXP = /\/\/github\.com\/github\/(?!docs[/'"\n])([\w-.]+)/gi diff --git a/tests/routing/deprecated-enterprise-versions.js b/tests/routing/deprecated-enterprise-versions.js index cbdfcd495b..d26fc4047c 100644 --- a/tests/routing/deprecated-enterprise-versions.js +++ b/tests/routing/deprecated-enterprise-versions.js @@ -3,7 +3,7 @@ import { describe, jest, test } from '@jest/globals' import enterpriseServerReleases from '../../lib/enterprise-server-releases.js' import { get, getDOM } from '../helpers/e2etest.js' import { SURROGATE_ENUMS } from '../../middleware/set-fastly-surrogate-key.js' -import { PREFERRED_LOCALE_COOKIE_NAME } from '../../middleware/detect-language.js' +import { PREFERRED_LOCALE_COOKIE_NAME } from '../../lib/constants.js' jest.useFakeTimers({ legacyFakeTimers: true }) diff --git a/tests/routing/redirects.js b/tests/routing/redirects.js index 4c6bdfffe7..760f69db5d 100644 --- a/tests/routing/redirects.js +++ b/tests/routing/redirects.js @@ -9,7 +9,7 @@ import enterpriseServerReleases, { import Page from '../../lib/page.js' import { get, head } from '../helpers/e2etest.js' import versionSatisfiesRange from '../../lib/version-satisfies-range.js' -import { PREFERRED_LOCALE_COOKIE_NAME } from '../../middleware/detect-language.js' +import { PREFERRED_LOCALE_COOKIE_NAME } from '../../lib/constants.js' const __dirname = path.dirname(fileURLToPath(import.meta.url)) diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md index 5c660e6ecb..abe756b715 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md @@ -32,7 +32,7 @@ Building and testing your code requires a server. You can build and test updates ## About continuous integration using {% data variables.product.prodname_actions %} {% ifversion ghae %}CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on runner systems that you host. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." -{% else %} CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on {% data variables.product.prodname_dotcom %}-hosted virtual machines, or on machines that you host yourself. For more information, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)" and "[About self-hosted runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)." +{% else %} CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on {% data variables.product.prodname_dotcom %}-hosted virtual machines, or on machines that you host yourself. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)." {% endif %} You can configure your CI workflow to run when a {% data variables.product.prodname_dotcom %} event occurs (for example, when new code is pushed to your repository), on a set schedule, or when an external event occurs using the repository dispatch webhook. diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md index 6075f8657b..b86dc1810e 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md @@ -28,8 +28,8 @@ Esta guía te muestra cómo crear un flujo de trabajo que realice integración c Para encontrar una lista completa de versiones disponibles de Xamarin SDK en los ejecutores de macOS hospedados en {% data variables.product.prodname_actions %}, consulta la documentación: -* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles) -* [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles) +* [macOS 10.15](https://github.com/actions/runner-images/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles) +* [macOS 11](https://github.com/actions/runner-images/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles) {% data reusables.actions.macos-runner-preview %} diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md index 12cea1c95f..28423b9820 100644 --- a/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md @@ -39,7 +39,7 @@ You may find it helpful to have a basic understanding of {% data variables.produ {% ifversion ghae %} - "[Docker container filesystem](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)." {% else %} -- "[Virtual environments for {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners#docker-container-filesystem)" +- "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)" {% endif %} Before you begin, you'll need to create a {% data variables.product.prodname_dotcom %} repository. diff --git a/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 74b7a7aee9..05a1ccc806 100644 --- a/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -74,7 +74,7 @@ Por ejemplo, si un flujo de trabajo definió las entradas de `numOctocats` y `oc ### `inputs..required` -**Requerido** Un `boolean` (booleano) para indicar si la acción requiere el parámetro de entrada. Establecer en `true` cuando se requiera el parámetro. +**Opcional** Un `boolean` para indicar si la acción requiere el parámetro de entrada. Establecer en `true` cuando se requiera el parámetro. ### `inputs..default` diff --git a/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md index 6b6bf67220..7a9e2cd47d 100644 --- a/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md +++ b/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md @@ -27,7 +27,7 @@ Puedes configurr ambientes con reglas de protección y secretos. Cuando un job d **Nota:** Solo puedes configurar ambientes para repositorios públicos. Si conviertes un repositorio de público a privado, cualquier regla de protección o secretos de ambiente que hubieses configurado se ingorarán y no podrás configurar ningún ambiente. Si conviertes tu repositorio en público nuevamente, tendrás acceso a cualquier regla de protección y secreto de ambiente que hubieras configurado previamente. -Las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} pueden configurar ambientes para los repositorios privados. Para obtener más información, consulta la sección [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment). {% data reusables.enterprise.link-to-ghec-trial %} +Organizations with {% data variables.product.prodname_team %} and users with {% data variables.product.prodname_pro %} can configure environments for private repositories. Para obtener más información, consulta "Productos de [{% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/githubs-products)". {% endnote %} {% endif %} @@ -72,7 +72,7 @@ Los secretos que se almacenan en un ambiente sólo se encuentran disponibles par {% ifversion fpt or ghec %} {% note %} -**Nota:** Para crear un ambiente en un repositorio privado, tu organización debe utilizar {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} +**Note:** Creation of an environment in a private repository is available to organizations with {% data variables.product.prodname_team %} and users with {% data variables.product.prodname_pro %}. {% endnote %} {% endif %} diff --git a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md index cdc6ecb312..6a020ca344 100644 --- a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md @@ -37,7 +37,7 @@ Cuando migres desde CircleCI, considera las siguientes diferencias: - El paralelismo automático de pruebas de CircleCI agrupa las pruebas automáticamente de acuerdo con las reglas que el usuario haya especificado o el historial de información de tiempos. Esta funcionalidad no se incluye en {% data variables.product.prodname_actions %}. - Las acciones que se ejecutan en los contenedores de Docker distinguen entre problemas de permisos, ya que los contenedores tienen un mapeo de usuarios diferente. Puedes evitar muchos de estos problemas si no utilizas la instrucción `USER` en tu *Dockerfile*. {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} -{% else %}Para obtener más información acerca del sistema de archivos de Docker en los ejecutores hospedados en {% data variables.product.product_name %}, consulta la sección "[Ambientes virtuales para los ejecutores hospedados en {% data variables.product.product_name %}](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)". +{% else %}Para obtener más información sobre el sistema de archivos de Docker en los ejecutores hospedados en {% data variables.product.product_name %}, consulta la sección [Acerca de los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)". {% endif %} ## Migrar flujos de trabajo y jobs @@ -66,10 +66,10 @@ Para obtener información sobre el sistema de archivos de Docker, consulta la se {% data reusables.actions.self-hosted-runners-software %} {% else %} -Para obtener más información acerca del sistema de archivos de Docker, consulta la sección "[Ambientes virtuales para los ejecutores hospedados en {% data variables.product.product_name %}](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)". +Para obtener más información sobre el sistema de archivos de Docker, consulta la sección "[Acerca de los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)". Para obtener más información sobre las herramientas y paquetes disponibles en -los ambientes hospedados en {% data variables.product.prodname_dotcom %}, consulta la sección "[Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". +las imágenes de los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, consulta la sección "[Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". {% endif %} ## Utilizar variables y secretos @@ -287,7 +287,8 @@ jobs: steps: # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. - # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem + # See https://docs.github.com/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem + - name: Setup file system permissions run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp - uses: {% data reusables.actions.action-checkout %} diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md index db088ec52a..fc02c3d04e 100644 --- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md +++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md @@ -16,26 +16,26 @@ shortTitle: Agregar una insignia de estado {% note %} -**Note**: Workflow badges in a private repository are not accessible externally, so you won't be able to embed them or link to them from an external site. +**Nota**: No se puede acceder a las insignias de flujo de trabajo desde el exterior hacia un repositorio privado, así que no tendrás que embeberlas ni enlazarlas desde un sitio externo. {% endnote %} {% data reusables.repositories.actions-workflow-status-badge-intro %} -To add a workflow status badge to your `README.md` file, first find the URL for the status badge you would like to display. Then you can use Markdown to display the badge as an image in your `README.md` file. For more information about image markup in Markdown, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#images)." +Para agregar una insignia de estado de flujo de trabajo a tu archivo `README.md`, primero encuentra la URL de la insignia de estado que te gustaría mostrar. Luego, puedes utilizar lenguaje de marcado para mostrar la insignia como imagen en tu archivo `README.md`. Para obtener más información sobre el marcado de imagen en el lenguaje de marcado, consulta la sección "[Escritura básica y sintaxis de formato](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#images)". ## Usar el nombre de archivo del flujo de trabajo -You can build the URL for a workflow status badge using the name of the workflow file: +Puedes compilar la URL para una insignia de estado de flujo de trabajo utilizando el nombre del archivo de flujo de trabajo: ``` {% ifversion fpt or ghec %}https://github.com{% else %}{% endif %}///actions/workflows//badge.svg ``` -To display the workflow status badge in your `README.md` file, use the Markdown markup for embedding images. For more information about image markup in Markdown, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#images)." +Para mostrar la insignia de estado de flujo de trabajo en tu archivo `README.md`, utiliza el lenguaje de marcado para embeber imágenes. Para obtener más información sobre el marcado de imagen en el lenguaje de marcado, consulta la sección "[Escritura básica y sintaxis de formato](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#images)". -For example, add the following Markdown to your `README.md` file to add a status badge for a workflow with the file path `.github/workflows/main.yml`. El `OWNER` del repositorio es la organización `github` y el nombre del `REPOSITORY` es `docs`. +Por ejemplo, agrega el siguiente lenguaje de marcado a tu archivo `README.md` para agregar una insignia de estado para un flujo de trabajo con la ruta de archivo `.github/workflows/main.yml`. El `OWNER` del repositorio es la organización `github` y el nombre del `REPOSITORY` es `docs`. ```markdown ![flujo de trabajo de ejemplo](https://github.com/github/docs/actions/workflows/main.yml/badge.svg) @@ -43,9 +43,9 @@ For example, add the following Markdown to your `README.md` file to add a status ## Utilizar el parámetro `branch` -To display the status of a workflow run for a specific branch, add `?branch=` to the end of the status badge URL. +Para mostrar el estado de una ejecución de flujo de trabajo para una rama específica, agrega `?branch=` al final de la URL de la insignia de estado. -For example, add the following Markdown to your `README.md` file to display a status badge for a branch with the name `feature-1`. +Por ejemplo, agrega el siguiente lenguaje de marcado a tu archivo `README.md` para mostrar una insignia de estado para una rama con el nombre `feature-1`. ```markdown ![example branch parameter](https://github.com/github/docs/actions/workflows/main.yml/badge.svg?branch=feature-1) @@ -53,9 +53,9 @@ For example, add the following Markdown to your `README.md` file to display a st ## Utilizar el parámetro `event` -To display the status of workflow runs triggered by the `push` event, add `?event=push` to the end of the status badge URL. +Para mostrar el estado de las ejecuciones de flujo de trabajo que se activan con el evento `push`, agrega `?event=push` al final de la URL de la insignia de estado. -For example, add the following Markdown to your `README.md` file to display a badge with the status of workflow runs triggered by the `push` event, which will show the status of the build for the current state of that branch. +Por ejemplo, agrega el siguiente lenguaje de marcado a tu archivo `README.md` para mostrar la insignia con el estado de las ejecuciones de flujo de trabajo que activa el evento `push`, lo cual te mostrará el estado de la compilación para el estado actual de dicha rama. ```markdown ![example event parameter](https://github.com/github/docs/actions/workflows/main.yml/badge.svg?event=push) diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md index d29528c1d9..ea5c4d477b 100644 --- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md +++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md @@ -27,7 +27,7 @@ Si falla la ejecución de su flujo de trabajo, puedes ver qué paso provocó el Adicionalmente a los pasos que se configuraron en el archivo de flujo de trabajo, {% data variables.product.prodname_dotcom %} agrega dos pasos adicionales a cada job para configurar y completar la ejecución del flujo de trabajo. Estos pasos se registran en la ejecución del flujo de trabajo con los nombres de "Set up job" y "Complete job". -Para jobs que se ejecutan en ejecutores hospedados en {% data variables.product.prodname_dotcom %}, "Set up job" registra los detalles del ambiente virtual del ejecutor, e incluye un enlace a la lista de herramientas pre-instaladas que estuvieron presentes en la máquina del ejecutor. +For jobs run on {% data variables.product.prodname_dotcom %}-hosted runners, "Set up job" records details of the runner image, and includes a link to the list of preinstalled tools that were present on the runner machine. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index 68a40c5401..dcfa57bf9b 100644 --- a/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -105,20 +105,20 @@ Workflow logs list the runner used to run a job. For more information, see "[Vie The software tools included in {% data variables.product.prodname_dotcom %}-hosted runners are updated weekly. The update process takes several days, and the list of preinstalled software on the `main` branch is updated after the whole deployment ends. ### Preinstalled software -Workflow logs include a link to the preinstalled tools on the exact runner. To find this information in the workflow log, expand the `Set up job` section. Under that section, expand the `Virtual Environment` section. The link following `Included Software` will describe the preinstalled tools on the runner that ran the workflow. +Workflow logs include a link to the preinstalled tools on the exact runner. To find this information in the workflow log, expand the `Set up job` section. Under that section, expand the `Runner Image` section. The link following `Included Software` will describe the preinstalled tools on the runner that ran the workflow. ![Installed software link](/assets/images/actions-runner-installed-software-link.png) For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." For the overall list of included tools for each runner operating system, see the links below: -* [Ubuntu 22.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2204-Readme.md) -* [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-Readme.md) -* [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-Readme.md) -* [Windows Server 2022](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md) -* [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md) -* [macOS 12](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-12-Readme.md) -* [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md) -* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) +* [Ubuntu 22.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2204-Readme.md) +* [Ubuntu 20.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2004-Readme.md) +* [Ubuntu 18.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu1804-Readme.md) (deprecated) +* [Windows Server 2022](https://github.com/actions/runner-images/blob/main/images/win/Windows2022-Readme.md) +* [Windows Server 2019](https://github.com/actions/runner-images/blob/main/images/win/Windows2019-Readme.md) +* [macOS 12](https://github.com/actions/runner-images/blob/main/images/macos/macos-12-Readme.md) +* [macOS 11](https://github.com/actions/runner-images/blob/main/images/macos/macos-11-Readme.md) +* [macOS 10.15](https://github.com/actions/runner-images/blob/main/images/macos/macos-10.15-Readme.md) {% data variables.product.prodname_dotcom %}-hosted runners include the operating system's default built-in tools, in addition to the packages listed in the above references. For example, Ubuntu and macOS runners include `grep`, `find`, and `which`, among other default tools. @@ -128,7 +128,7 @@ We recommend using actions to interact with the software installed on runners. T - Usually, actions provide more flexible functionality like versions selection, ability to pass arguments, and parameters - It ensures the tool versions used in your workflow will remain the same regardless of software updates -If there is a tool that you'd like to request, please open an issue at [actions/virtual-environments](https://github.com/actions/virtual-environments). This repository also contains announcements about all major software updates on runners. +If there is a tool that you'd like to request, please open an issue at [actions/runner-images](https://github.com/actions/runner-images). This repository also contains announcements about all major software updates on runners. ### Installing additional software diff --git a/translations/es-ES/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md b/translations/es-ES/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md index 4b325323cd..7d1dff22d7 100644 --- a/translations/es-ES/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md +++ b/translations/es-ES/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md @@ -20,7 +20,7 @@ miniTocMaxHeadingLevel: 3 Las ejecuciones de flujo de trabajo a menudo reutilizan las mismas salidas o dependencias descargadas de una ejecución a otra. Por ejemplo, las herramientas de administración de paquetes y dependencias como Maven, Gradle, npm y Yarn mantienen una caché local de las dependencias descargadas. -{% ifversion fpt or ghec %} Los jobs en los ejecutores hospedados en {% data variables.product.prodname_dotcom %} inician en un ambiente virtual limpio y deben descargar dependencias en cada ocasión, lo que provoca que una mayor utilización de red, un tiempo de ejecución más largo y un costo incrementado. {% endif %}Para ayudar a agilizar el tiempo que toma el recrear archivos como dependencias, {% data variables.product.prodname_dotcom %} puede almacenar los archivos en caché que utilizas frecuentemente en los flujos de trabajo. +{% ifversion fpt or ghec %} Jobs on {% data variables.product.prodname_dotcom %}-hosted runners start in a clean runner image and must download dependencies each time, causing increased network utilization, longer runtime, and increased cost. {% endif %}Para ayudar a agilizar el tiempo que toma el recrear archivos como dependencias, {% data variables.product.prodname_dotcom %} puede almacenar los archivos en caché que utilizas frecuentemente en los flujos de trabajo. Para almacenar las dependencias en caché para un job, puedes utilizar la {% data variables.product.prodname_dotcom %}acción de [cache`` de ](https://github.com/actions/cache). La acción crea y restablece un caché identificado con una llave única. Como alternativa, si estás almacenando los siguientes administradores de paquetes en caché, el utilizar sus acciones respectivas de setup-* requiere de una configuración mínima y creará y restablecerá los cachés de dependencia para ti. diff --git a/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md index 65e0259043..2607f856d8 100644 --- a/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md +++ b/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md @@ -538,6 +538,7 @@ You can override the default shell settings in the runner's operating system usi | Supported platform | `shell` parameter | Description | Command run internally | |--------------------|-------------------|-------------|------------------------| +| Linux / macOS | unspecified | The default shell on non-Windows platforms. Note that this runs a different command to when `bash` is specified explicitly. If `bash` is not found in the path, this is treated as `sh`. | `bash -e {0}` | | All | `bash` | The default shell on non-Windows platforms with a fallback to `sh`. When specifying a bash shell on Windows, the bash shell included with Git for Windows is used. | `bash --noprofile --norc -eo pipefail {0}` | | All | `pwsh` | The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `pwsh -command ". '{0}'"` | | All | `python` | Executes the python command. | `python {0}` | @@ -793,11 +794,11 @@ strategy: fail-fast: false matrix: node: [13, 14] - os: [macos-latest, ubuntu-18.04] + os: [macos-latest, ubuntu-latest] experimental: [false] include: - node: 15 - os: ubuntu-18.04 + os: ubuntu-latest experimental: true ``` {% endraw %} diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md index 7df863eee1..7d0fbc474c 100644 --- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md +++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md @@ -146,7 +146,7 @@ Opcionalmente, puedes crear herramientas personalizadas para escalar automática - "Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando {% data variables.product.prodname_github_connect %}" en la documentación de [{% data variables.product.prodname_ghe_server %}](/enterprise-server@latest/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect) o de [{% data variables.product.prodname_ghe_managed %}](/github-ae@latest//admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect) {%- endif %} -- Puedes personalizar el software disponible en tus máquinas ejecutoras auto-hospedadas o configurar tus ejecutores para que ejecuten software similar a aquellos hospedados en {% data variables.product.company_short %}{% ifversion ghes or ghae %} disponible para los clientes que utilizan {% data variables.product.prodname_dotcom_the_website %}{% endif %}. El software que impulsa las máquinas ejecutoras para {% data variables.product.prodname_actions %} es de código abierto. Para obtener más información, consulta los repositorios [`actions/runner`](https://github.com/actions/runner) y [`actions/virtual-environments`](https://github.com/actions/virtual-environments). +- Puedes personalizar el software disponible en tus máquinas ejecutoras auto-hospedadas o configurar tus ejecutores para que ejecuten software similar a aquellos hospedados en {% data variables.product.company_short %}{% ifversion ghes or ghae %} disponible para los clientes que utilizan {% data variables.product.prodname_dotcom_the_website %}{% endif %}. El software que impulsa las máquinas ejecutoras para {% data variables.product.prodname_actions %} es de código abierto. For more information, see the [`actions/runner`](https://github.com/actions/runner) and [`actions/runner-images`](https://github.com/actions/runner-images) repositories. ## Leer más diff --git a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index 7a14fec590..18b72a61a6 100644 --- a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -31,7 +31,7 @@ Puedes poblar el caché de la herramienta del ejecutor si ejecutas un flujo de t {% note %} -**Nota:** Solo puedes utilizar un caché de la herramienta del ejecutor hospedado en {% data variables.product.prodname_dotcom %} para un ejecutor auto-hospedado que tenga un sistema operativo y arquitectura idénticos. Por ejemplo, si estás utilizando un ejecutor hospedado en {% data variables.product.prodname_dotcom %} con `ubuntu-18.04` para generar un caché de la herramienta, tu ejecutor auto-hospedado también debe ser una máquina con Ubuntu 18.04 de 64 bits. Para obtener más información sobre los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, consulta la sección "[Ambientes virtuales para los ejecutores hospedados en GitHub](/free-pro-team@latest/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)". +**Nota:** Solo puedes utilizar un caché de la herramienta del ejecutor hospedado en {% data variables.product.prodname_dotcom %} para un ejecutor auto-hospedado que tenga un sistema operativo y arquitectura idénticos. Por ejemplo, si estás utilizando un ejecutor hospedado en {% data variables.product.prodname_dotcom %} con `ubuntu-22.04` para generar un caché de la herramienta, tu ejecutor auto-hospedado también debe ser una máquina con Ubuntu 22.04 de 64 bits. Para obtener más información sobre los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, consulta la sección "[Acerca de los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/free-pro-team@latest/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)". {% endnote %} @@ -46,14 +46,14 @@ Puedes poblar el caché de la herramienta del ejecutor si ejecutas un flujo de t 1. En {% data variables.product.prodname_dotcom_the_website %}, navega a un repositorio que puedas utilizar para ejecutar un flujo de trabajo de {% data variables.product.prodname_actions %}. 1. Crea un archivo de flujo de trabajo nuevo en la carpeta `.github/workflows` del repositorio, el cual cargue un artefacto que contenga el caché de la herramienta del ejecutor hospedado en {% data variables.product.prodname_dotcom %}. - El siguiente ejemplo muestra un flujo de trabajo que carga el caché de la herramienta para un ambiente de Ubuntu 18.04 utilizando la acción `setup-node` con las versiones 10 y 12 de Node.js. + El siguiente ejemplo muestra un flujo de trabajo que carga el caché de la herramienta para un ambiente de Ubuntu 22.04 utilizando la acción `setup-node` con las versiones 10 y 12 de Node.js. ```yaml name: Upload Node.js 10 and 12 tool cache on: push jobs: upload_tool_cache: - runs-on: ubuntu-18.04 + runs-on: ubuntu-22.04 steps: - name: Clear any existing tool cache run: | diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md b/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md index 33498deabe..138b4a96b7 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md +++ b/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md @@ -30,6 +30,8 @@ redirect_from: If your enterprise members manage their own user accounts on {% data variables.product.product_location %}, you can configure SAML authentication as an additional access restriction for your enterprise or organization. {% data reusables.saml.dotcom-saml-explanation %} +{% data reusables.saml.saml-accounts %} + {% data reusables.saml.about-saml-enterprise-accounts %} Para obtener más información, consulta la sección "[Configurar el incio de sesión único de SAML para tu empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)". Alternatively, you can provision and manage the accounts of your enterprise members with {% data variables.product.prodname_emus %}. Para ayudarte a determinar si el SSO de SAML o las {% data variables.product.prodname_emus %} son mejores para tu empresa, consulta la sección "[Acerca de la autetnicación para tu empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)". diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md index 025a74c7a2..96aa91badf 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md @@ -29,7 +29,11 @@ redirect_from: {% ifversion ghec %} -{% data reusables.saml.dotcom-saml-explanation %}Para obtener más información, consulta "[Acerca de la administración de identidad y accesos con el inicio de sesión único de SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)". +{% data reusables.saml.dotcom-saml-explanation %} + +{% data reusables.saml.saml-accounts %} + +Para obtener más información, consulta la sección "[Acerca de la administración de identidad y accesos con el inicio de sesión único de SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)". {% data reusables.saml.about-saml-enterprise-accounts %} diff --git a/translations/es-ES/content/admin/overview/about-enterprise-accounts.md b/translations/es-ES/content/admin/overview/about-enterprise-accounts.md index 684e032555..60793424f8 100644 --- a/translations/es-ES/content/admin/overview/about-enterprise-accounts.md +++ b/translations/es-ES/content/admin/overview/about-enterprise-accounts.md @@ -35,7 +35,7 @@ The enterprise account on {% ifversion ghes %}{% data variables.product.product_ Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." {% ifversion ghec %} -Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings. +Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings. For more information, see "[Adding organizations to your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)." {% endif %} Your enterprise account allows you to manage and enforce policies for all the organizations owned by the enterprise. {% data reusables.enterprise.about-policies %} For more information, see "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)." diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md index 437374e8e5..0e4046bd7f 100644 --- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md @@ -14,13 +14,14 @@ topics: - Enterprise - Organizations shortTitle: Add organizations +permissions: Enterprise owners can add organizations to an enterprise. --- ## About organizations Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." -Enterprise owners can create new organizations within an enterprise account's settings or invite existing organizations to join an enterprise. To add an organization to your enterprise, you must create the organization from within the enterprise account settings. +You can add a new or existing organization to your enterprise in your enterprise account's settings. You can only add organizations this way to an existing enterprise account. {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." diff --git a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md index 1427df4257..2e352ad001 100644 --- a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md +++ b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md @@ -29,24 +29,24 @@ Los elementos de la tabla a continuación se pueden migrar con un repositorio. N {% data reusables.enterprise_migrations.fork-persistence %} -| Datos asociados con un repositorio migrado | Notas | -| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Usuarios | Las **@menciones** de los usuarios se reescriben para coincidir con el objetivo. | -| Organizaciones | El nombre y los datos de una organización se migran. | -| Repositorios | Los enlaces a árboles Git, blobs, confirmaciones de cambios y líneas se reescriben para coincidir con el objetivo. El migrador sigue un máximo de tres redirecciones de repositorio. | -| Wikis | Todos los datos de la wiki se migran. | -| Equipos | Las **@menciones** de los equipos se reescriben para coincidir con el objetivo. | -| Hitos | Los registros horarios se conservan. | -| Tableros de proyecto | Los tableros de proyectos asociados con el repositorio y con la organización que posee el repositorio se migran. | -| Problemas | Las referencias de propuestas y los registros horarios se conservan. | -| Comentarios de propuestas | Las referencias cruzadas a los comentarios se reescriben para la instancia de destino. | -| Solicitudes de cambios | Las referencias cruzadas a las solicitudes de extracción se reescriben para coincidir con el objetivo. Los registros horarios se conservan. | -| Revisiones de solicitudes de extracción | Las revisiones de solicitudes de extracción y los datos asociados se migran. | -| Comentarios sobre revisiones de solicitudes de extracción | Las referencias cruzadas a los comentarios se reescriben para la instancia de destino. Los registros horarios se conservan. | -| Comentarios sobre confirmación de cambios | Las referencias cruzadas a los comentarios se reescriben para la instancia de destino. Los registros horarios se conservan. | -| Lanzamientos | Todos los datos de las versiones se migran. | -| Medidas adoptadas en las solicitudes de extracción o propuestas | Todas las modificaciones a las solicitudes de extracción o propuestas, como la asignación de usuarios, el cambio de nombre de título y la modificación de etiquetas se conservan, junto con los registros horarios de cada acción. | -| Archivos adjuntos | [Los archivos adjuntos a las propuestas y las solicitudes de extracción](/articles/file-attachments-on-issues-and-pull-requests) se migran. Puedes elegir inhabilitar esta opción como parte de la migración. | -| Webhooks | Solo se migran los webhooks activos. | -| Llaves de implementación de repositorios | Las llaves de implementación de repositorios se migran. | -| Ramas protegidas | La configuración de las ramas protegidas y los datos asociados se migran. | +| Datos asociados con un repositorio migrado | Notas | +| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Usuarios | Las **@menciones** de los usuarios se reescriben para coincidir con el objetivo. | +| Organizaciones | El nombre y los datos de una organización se migran. | +| Repositorios | Los enlaces a árboles Git, blobs, confirmaciones de cambios y líneas se reescriben para coincidir con el objetivo. El migrador sigue un máximo de tres redirecciones de repositorio. Internal repositories are migrated as private repositories. Archive status is unset. | +| Wikis | Todos los datos de la wiki se migran. | +| Equipos | Las **@menciones** de los equipos se reescriben para coincidir con el objetivo. | +| Hitos | Los registros horarios se conservan. | +| Tableros de proyecto | Los tableros de proyectos asociados con el repositorio y con la organización que posee el repositorio se migran. | +| Problemas | Las referencias de propuestas y los registros horarios se conservan. | +| Comentarios de propuestas | Las referencias cruzadas a los comentarios se reescriben para la instancia de destino. | +| Solicitudes de cambios | Las referencias cruzadas a las solicitudes de extracción se reescriben para coincidir con el objetivo. Los registros horarios se conservan. | +| Revisiones de solicitudes de extracción | Las revisiones de solicitudes de extracción y los datos asociados se migran. | +| Comentarios sobre revisiones de solicitudes de extracción | Las referencias cruzadas a los comentarios se reescriben para la instancia de destino. Los registros horarios se conservan. | +| Comentarios sobre confirmación de cambios | Las referencias cruzadas a los comentarios se reescriben para la instancia de destino. Los registros horarios se conservan. | +| Lanzamientos | Todos los datos de las versiones se migran. | +| Medidas adoptadas en las solicitudes de extracción o propuestas | Todas las modificaciones a las solicitudes de extracción o propuestas, como la asignación de usuarios, el cambio de nombre de título y la modificación de etiquetas se conservan, junto con los registros horarios de cada acción. | +| Archivos adjuntos | [Los archivos adjuntos a las propuestas y las solicitudes de extracción](/articles/file-attachments-on-issues-and-pull-requests) se migran. Puedes elegir inhabilitar esta opción como parte de la migración. | +| Webhooks | Solo se migran los webhooks activos. | +| Llaves de implementación de repositorios | Las llaves de implementación de repositorios se migran. | +| Ramas protegidas | La configuración de las ramas protegidas y los datos asociados se migran. | diff --git a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index 9dbe1a8590..0680687988 100644 --- a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: Acerca de la autenticación con el inicio de sesión único de SAML -intro: 'Puedes acceder a {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}una organización que utilice el inicio de sesión único (SSO) de SAML{% endif %}s si te autenticas {% ifversion ghae %} con el inicio de sesión único (SSO) de SAML {% endif %}a través de un proveedor de identidad (IdP).{% ifversion ghec %} Después de que te autentiques exitosamente con el IdP desde {% data variables.product.product_name %}, debes autorizar cualquier token de acceso personal, llave SSH o {% data variables.product.prodname_oauth_app %} a la que quieras acceder en los recursos de la organización.{% endif %}' +intro: 'You can access {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).' redirect_from: - /articles/about-authentication-with-saml-single-sign-on - /github/authenticating-to-github/about-authentication-with-saml-single-sign-on @@ -29,10 +29,9 @@ Si nopuedes acceder a {% data variables.product.product_name %}, contacta al pro {% data reusables.saml.dotcom-saml-explanation %} Los propietarios de las organizaciones pueden invitar a tu cuenta personal de {% data variables.product.prodname_dotcom %} para que se una a sus organizaciones que utilicen el SSO de SAML, lo cual te permitirá contribuir con la organización y retener tu identidad existente y las contribuciones en {% data variables.product.prodname_dotcom %}. -Si eres miembro de una {% data variables.product.prodname_emu_enterprise %}, utilizarás una cuenta nueva que se aprovisionará para ti. {% data reusables.enterprise-accounts.emu-more-info-account %} +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will instead use a new account that is provisioned for you and controlled by your enterprise. {% data reusables.enterprise-accounts.emu-more-info-account %} - -Cuando accedes a recurso dentro de la organización que utiliza SAML SSO, , {% data variables.product.prodname_dotcom %} te redirigirá a el SAML IdP de la organización para autenticarte. Después de que te autentiques exitosamente con tu cuenta en el IdP, este te redirigirá de vuelta a {% data variables.product.prodname_dotcom %}, en donde podrás acceder a los recursos de la organización. +When you access private resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. Después de que te autentiques exitosamente con tu cuenta en el IdP, este te redirigirá de vuelta a {% data variables.product.prodname_dotcom %}, en donde podrás acceder a los recursos de la organización. {% data reusables.saml.outside-collaborators-exemption %} @@ -40,6 +39,16 @@ Si te has autenticado recientemente con tu SAML IdP de la organización en tu na {% data reusables.saml.you-must-periodically-authenticate %} +## Linked SAML identities + +When you authenticate with your IdP account and return to {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_dotcom %} will record a link in the organization or enterprise between your {% data variables.product.prodname_dotcom %} personal account and the SAML identity you signed into. This linked identity is used to validate your membership in that organization, and depending on your organization or enterprise setup, is also used to determine which organizations and teams you're a member of as well. Each {% data variables.product.prodname_dotcom %} account can be linked to exactly one SAML identity per organization. Likewise, each SAML identity can be linked to exactly one {% data variables.product.prodname_dotcom %} account in an organization. + +If you sign in with a SAML identity that is already linked to another {% data variables.product.prodname_dotcom %} account, you will receive an error message indicating that you cannot sign in with that SAML identity. This situation can occur if you are attempting to use a new {% data variables.product.prodname_dotcom %} account to work inside of your organization. If you didn't intend to use that SAML identity with that {% data variables.product.prodname_dotcom %} account, then you'll need to sign out of that SAML identity and then repeat the SAML login. If you do want to use that SAML identity with your {% data variables.product.prodname_dotcom %} account, you'll need to ask your admin to unlink your SAML identity from your old account, so that you can link it to your new account. Depending on the setup of your organization or enterprise, your admin may also need to reassign your identity within your SAML provider. Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)". + +If the SAML identity you sign in with does not match the SAML identity that is currently linked to your {% data variables.product.prodname_dotcom %} account, you'll receive a warning that you are about to relink your account. Because your SAML identity is used to govern access and team membership, continuing with the new SAML identity can cause you to lose access to teams and organizations inside of {% data variables.product.prodname_dotcom %}. Only continue if you know that you're supposed to use that new SAML identity for authentication in the future. + +## Authorizing PATs and SSH keys with SAML SSO + Para usar la API o Git en la línea de comandos para acceder a contenido protegido en una organización que usa SAML SSO, necesitarás usar un token de acceso personal autorizado a través de HTTPS o una clave SSH autorizada. Si no tienes un token de acceso personal ni una clave SSH, puedes crear un token de acceso personal para la línea de comandos o generar una clave SSH nueva. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" o "[Generar una nueva llave SSH y añadirla al agente de ssh](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md index 3bf5f9be29..55caa8e709 100644 --- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md +++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md @@ -14,8 +14,6 @@ topics: - SSH --- -## Acerca de SSH - {% data reusables.ssh.about-ssh %} Para obtener más información sobre SSH, consulta la página de [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) en Wikipedia. Cuando configuras SSH, necesitarás generar una llave SSH privada nueva y agregarla al agente SSH. También debes agregar la llave SSH pública a tu cuenta en {% data variables.product.product_name %} antes de que utilices la llave para autenticarte. Para obtener más información, consulta las secciones "[Generar una llave SSH nueva y agregarla al ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" y "[Agregar una llave SSH nueva a tu cuenta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)". diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md index 49a17a47ff..1bf30d4513 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md @@ -23,7 +23,7 @@ To maintain the security of your account when you perform a potentially sensitiv - Authorization of a third-party application - Addition of a new SSH key -After you authenticate to perform a sensitive action, your session is temporarily in "sudo mode." In sudo mode, you can perform sensitive actions without authentication. {% data variables.product.product_location %} will wait a few hours before prompting you for authentication again. During this time, any sensitive action that you perform will reset the timer. +After you authenticate to perform a sensitive action, your session is temporarily in "sudo mode." In sudo mode, you can perform sensitive actions without authentication. {% data variables.product.product_name %} will wait a few hours before prompting you for authentication again. During this time, any sensitive action that you perform will reset the timer. {% ifversion ghes %} @@ -41,13 +41,16 @@ After you authenticate to perform a sensitive action, your session is temporaril To confirm access for sudo mode, you {% ifversion totp-and-mobile-sudo-challenge %}can{% else %}must{% endif %} authenticate with your password.{% ifversion totp-and-mobile-sudo-challenge %} Optionally, you can use a different authentication method, like {% ifversion fpt or ghec %}a security key, {% data variables.product.prodname_mobile %}, or a 2FA code{% elsif ghes %}a security key or a 2FA code{% endif %}.{% endif %} -{% ifversion totp-and-mobile-sudo-challenge %} +{%- ifversion totp-and-mobile-sudo-challenge %} - [Confirming access using a security key](#confirming-access-using-a-security-key) {%- ifversion fpt or ghec %} - [Confirming access using GitHub Mobile](#confirming-access-using-github-mobile) {%- endif %} - [Confirming access using a 2FA code](#confirming-access-using-a-2fa-code) - [Confirming access using your password](#confirming-access-using-your-password) +{%- endif %} + +{% ifversion totp-and-mobile-sudo-challenge %} ### Confirming access using a security key @@ -57,8 +60,6 @@ When prompted to authenticate for sudo mode, click **Use security key**, then fo ![Screenshot of security key option for sudo mode](/assets/images/help/settings/sudo_mode_prompt_security_key.png) -{% endif %} - {% ifversion fpt or ghec %} ### Confirming access using {% data variables.product.prodname_mobile %} @@ -75,11 +76,9 @@ You must install and sign into {% data variables.product.prodname_mobile %} to c {% endif %} -{% ifversion totp-and-mobile-sudo-challenge %} - ### Confirming access using a 2FA code -You must configure 2FA using a TOTP mobile app{% ifversion fpt or ghec %} or text messages{% endif %} to confirm access to your account for sudo mode using a 2FA code. Para obtener más información, consulta "[Configurar autenticación de dos factores](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-totp-mobile-app)". +You must configure 2FA using a TOTP mobile app{% ifversion fpt or ghec %} or text messages{% endif %} to confirm access to your account for sudo mode using a 2FA code. Para obtener más información, consulta "[Configurar autenticación de dos factores](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)". When prompted to authenticate for sudo mode, type the authentication code from your TOTP mobile app{% ifversion fpt or ghec %} or the text message{% endif %}, then click **Verify**. diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md index 1cfabdf8af..7d7f13b058 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md @@ -34,11 +34,11 @@ Debes ejecutar a {% data variables.product.prodname_codeql %} dentro del mismo c ## Dependencias -Es posible que tengas alguna dificultad para ejecutar el {% data variables.product.prodname_code_scanning %} si el contenedor que estás utilizando carece de ciertas dependencias (Por ejemplo, Git debe instalarse y agregarse a la variable PATH). Si te encuentras con algún problema en las dependencias, revisa la lista de software que habitualmente se incluye en los ambientes virtuales de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta los archivos `readme` específicos de la versión en estas ubicaciones: +Es posible que tengas alguna dificultad para ejecutar el {% data variables.product.prodname_code_scanning %} si el contenedor que estás utilizando carece de ciertas dependencias (Por ejemplo, Git debe instalarse y agregarse a la variable PATH). If you encounter dependency issues, review the list of software typically included on {% data variables.product.prodname_dotcom %}'s runner images. Para obtener más información, consulta los archivos `readme` específicos de la versión en estas ubicaciones: -* Linux: https://github.com/actions/virtual-environments/tree/main/images/linux -* macOS: https://github.com/actions/virtual-environments/tree/main/images/macos -* Windows: https://github.com/actions/virtual-environments/tree/main/images/win +* Linux: https://github.com/actions/runner-images/tree/main/images/linux +* macOS: https://github.com/actions/runner-images/tree/main/images/macos +* Windows: https://github.com/actions/runner-images/tree/main/images/win ## Ejemplo de flujo de trabajo diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index 48afabe62d..9e7b737857 100644 --- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -89,7 +89,7 @@ Para los repositorios en donde están habilitadas las {% data variables.product. ## Acceder a las {% data variables.product.prodname_dependabot_alerts %} -Puedes ver todas las alertas que afectan un proyecto en particular{% ifversion fpt or ghec %} en la pestaña de Seguridad del repositorio o{% endif %} en la gráfica de dependencias del repositorio. Para obtener más información, consulta la sección "[Ver y actualizar las {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)". +Puedes ver todas las alertas que afectan un proyecto en particular{% ifversion fpt or ghec %} en la pestaña de Seguridad del repositorio o{% endif %} en la gráfica de dependencias del repositorio. For more information, see "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)." Predeterminadamente, notificamos a las personas con permisos administrativos en los repositorios afectados sobre las {% data variables.product.prodname_dependabot_alerts %} nuevas. {% ifversion fpt or ghec %}{% data variables.product.product_name %} jamás divulga las dependencias inseguras de ningún repositorio al público. También puedes hacer que las personas o los equipos que trabajan con repositorios que te pertenezcan o para los cuales tengas permisos administrativos puedan ver las {% data variables.product.prodname_dependabot_alerts %}. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". {% endif %} @@ -103,5 +103,5 @@ También puedes ver todas las {% data variables.product.prodname_dependabot_aler ## Leer más - "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" -- "[Ver y actualizar las {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} {% ifversion fpt or ghec %}- "[Privacidad en {% data variables.product.prodname_dotcom %}](/get-started/privacy-on-github)"{% endif %} diff --git a/translations/es-ES/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/es-ES/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md index c08c7425b5..d0bcae3c70 100644 --- a/translations/es-ES/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/es-ES/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -93,7 +93,7 @@ Puedes configurar al {% data variables.product.prodname_dependabot %} para ignor ## Leer más - "[Acerca de las {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" -- "[Ver y actualizar las {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" +- "[Ver y actualizar{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" - "[Administrar la configuración de seguridad y de análisis para tu organización](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" - "[Solucionar problemas en la gráfica de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes > 3.2 %} - "[Solucionar problemas de los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/translations/es-ES/content/code-security/getting-started/github-security-features.md b/translations/es-ES/content/code-security/getting-started/github-security-features.md index 19978f53ae..bc033f52bd 100644 --- a/translations/es-ES/content/code-security/getting-started/github-security-features.md +++ b/translations/es-ES/content/code-security/getting-started/github-security-features.md @@ -58,8 +58,15 @@ The dependency graph allows you to explore the ecosystems and packages that your You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +{% ifversion security-overview-displayed-alerts %} +### Security overview + +The security overview allows you to review security configurations and alerts, making it easy to identify the repositories and organizations at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + +{% else %} ### Security overview for repositories -For all public repositories, the security overview shows which security features are enabled for the repository, and offers the option to configure any available security features that are not currently enabled. +The security overview shows which security features are enabled for the repository, and offers you the option of configuring any available security features that are not already enabled. +{% endif %} ## Available with {% data variables.product.prodname_GH_advanced_security %} @@ -67,7 +74,7 @@ For all public repositories, the security overview shows which security features The following {% data variables.product.prodname_GH_advanced_security %} features are available and free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can use the full set of features in any of their repositories. For a list of the features available with {% data variables.product.prodname_ghe_cloud %}, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/github-security-features#available-with-github-advanced-security). {% elsif ghec %} -Many {% data variables.product.prodname_GH_advanced_security %} features are available and free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations within an enterprise that has a {% data variables.product.prodname_GH_advanced_security %} license can use all the following features on their repositories. {% data reusables.advanced-security.more-info-ghas %} +Many {% data variables.product.prodname_GH_advanced_security %} features are available and free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations within an enterprise that have a {% data variables.product.prodname_GH_advanced_security %} license can use the following features on all their repositories. {% data reusables.advanced-security.more-info-ghas %} {% elsif ghes %} {% data variables.product.prodname_GH_advanced_security %} features are available for enterprises with a license for {% data variables.product.prodname_GH_advanced_security %}. The features are restricted to repositories owned by an organization. {% data reusables.advanced-security.more-info-ghas %} @@ -86,7 +93,7 @@ Automatically detect security vulnerabilities and coding errors in new or modifi Automatically detect leaked secrets across all public repositories. {% data variables.product.company_short %} informs the relevant service provider that the secret may be compromised. For details of the supported secrets and service providers, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)." {% endif %} -{% ifversion not fpt %} +{% ifversion ghec or ghes or ghae %} ### {% data variables.product.prodname_secret_scanning_GHAS_caps %} {% ifversion ghec %} @@ -100,12 +107,12 @@ Automatically detect tokens or credentials that have been checked into a reposit Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." -{% ifversion ghec or ghes or ghae %} -### Security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %}, enterprises,{% endif %} and teams +{% ifversion security-overview-displayed-alerts %} -{% ifversion ghec %} -Available only with a license for {% data variables.product.prodname_GH_advanced_security %}. -{% endif %} +{% elsif fpt %} + +{% else %} +### Security overview for organizations{% ifversion ghes > 3.4 or ghae-issue-6199 %}, enterprises,{% endif %} and teams Review the security configuration and alerts for your organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." {% endif %} diff --git a/translations/es-ES/content/code-security/getting-started/securing-your-organization.md b/translations/es-ES/content/code-security/getting-started/securing-your-organization.md index 155ef044ab..e560122037 100644 --- a/translations/es-ES/content/code-security/getting-started/securing-your-organization.md +++ b/translations/es-ES/content/code-security/getting-started/securing-your-organization.md @@ -123,7 +123,7 @@ For more information, see "[Managing security and analysis settings for your org {% data variables.product.prodname_code_scanning_capc %} is configured at the repository level. 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)." ## Next steps -You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." {% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} diff --git a/translations/es-ES/content/code-security/getting-started/securing-your-repository.md b/translations/es-ES/content/code-security/getting-started/securing-your-repository.md index 9d2fbc8235..ec95d618b2 100644 --- a/translations/es-ES/content/code-security/getting-started/securing-your-repository.md +++ b/translations/es-ES/content/code-security/getting-started/securing-your-repository.md @@ -132,7 +132,7 @@ You can set up {% data variables.product.prodname_code_scanning %} to automatica {% endif %} ## Next steps -You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." {% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} diff --git a/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md index d6d8def31e..481ec138e4 100644 --- a/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md +++ b/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md @@ -91,7 +91,7 @@ For more information about viewing and resolving {% data variables.product.prodn Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." -{% ifversion ghec or ghes %} +{% ifversion ghec or ghes or ghae-issue-5503 %} You can use the security overview to see an organization-level view of which repositories have enabled {% data variables.product.prodname_secret_scanning %} and the alerts found. For more information, see "[Viewing the security overview](/code-security/security-overview/viewing-the-security-overview)." {% endif %} diff --git a/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md b/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md index 1e0b1b7ad1..0fa41cda8d 100644 --- a/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md @@ -43,7 +43,7 @@ En el resumen de seguridad, puedes ver, clasificar y filtrar las alertas para en {% ifversion security-overview-views %} -En el resumen de seguridad, tanto a nivel de repositorio como de organización, hay vistas dedicadas para las características de seguridad específicas, tales como alertas de escaneo de secretos y de escaneo de código. Puedes utilizar estas vistas para limitar tu análisis a un conjunto de alertas específico y reducirlos aún más con un rango de filtros específico para cada vista. Por ejemplo, en la vista de alertas del escaneo de secretos, puedes utilizar el filtro `Secret type` para ver solo las alertas de escaneo de secretos para un secreto específico, como un Token de Acceso Personal de GitHub. A nivel de repositorio, puedes utilizar el resumen de seguridad para valorar el estado de seguridad actual del repositorio específico y configurar cualquier característica de seguridad adicional que no esté utilizando el repositorio. +In the security overview, there are dedicated views for each type of security alert, such as Dependabot, code scanning, and secret scanning alerts. Puedes utilizar estas vistas para limitar tu análisis a un conjunto de alertas específico y reducirlos aún más con un rango de filtros específico para cada vista. Por ejemplo, en la vista de alertas del escaneo de secretos, puedes utilizar el filtro `Secret type` para ver solo las alertas de escaneo de secretos para un secreto específico, como un Token de Acceso Personal de GitHub. A nivel de repositorio, puedes utilizar el resumen de seguridad para valorar el estado de seguridad actual del repositorio específico y configurar cualquier característica de seguridad adicional que no esté utilizando el repositorio. {% endif %} diff --git a/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md index d561ff68be..ddaeb9ccfe 100644 --- a/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md +++ b/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md @@ -25,6 +25,10 @@ shortTitle: Filtrar alertas Puedes utilizar filtros en el resumen de seguridad para reducir tu enfoque con base en una serie de factores, como el nivel de riesgo de la alerta, el tipo de esta y la habilitación de características. Hay diferentes filtros disponibles, dependiendo de la vista específica y de si tu análisis está a nivel de organización, equipo o repositorio. +{% note %} +{% data reusables.security-overview.information-varies-GHAS %} +{% endnote %} + ## Filtrar por repositorio Disponible en todas las vistas a nivel de organización y de equipo. diff --git a/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md b/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md index 573835b044..676d380b3d 100644 --- a/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md +++ b/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md @@ -21,6 +21,8 @@ shortTitle: Ver el resumen de seguridad {% data reusables.security-overview.beta %} {% endif %} +{% data reusables.security-overview.information-varies-GHAS %} + ## Visualizar el resumen de seguridad de una organización {% data reusables.organizations.navigate-to-org %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md b/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md index fff9351b0f..1d4e16a7ae 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md +++ b/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md @@ -34,7 +34,7 @@ Existen varias capacidades de seguridad que debe tener un sistema de compilació 3. Cada compilación debería iniciar en un ambiente nuevo, para que las compilaciones puestas en riesgo no persistan para afectar compilaciones futuras. -{% data variables.product.prodname_actions %} puede ayudarte a lograr estas capacidades. Las instrucciones de compilación se almacenan en tu repositorio, junto con tu código. Tú eliges en qué ambiente se ejecuta tu compilación, incluyendo los de Windows, Mac, Linux o los ejecutores que hospedas tú mismo. Cada compilación inicia con un ambiente virtual nuevo, lo que hace difícil que un ataque persista en tu ambiente de compilación. +{% data variables.product.prodname_actions %} puede ayudarte a lograr estas capacidades. Las instrucciones de compilación se almacenan en tu repositorio, junto con tu código. Tú eliges en qué ambiente se ejecuta tu compilación, incluyendo los de Windows, Mac, Linux o los ejecutores que hospedas tú mismo. Each build starts with a fresh runner image, making it difficult for an attack to persist in your build environment. Adicionalmente a los beneficios de seguridad, {% data variables.product.prodname_actions %} te permite activar compilaciones manualmente, regularmente o en eventos de git en tu repositorio para las compilaciones rápidas y frecuentes. diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index fd276a2d28..5984c9c70e 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -111,7 +111,7 @@ If a manifest or lock file is not processed, its dependencies are omitted from t ## Further reading - "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" -- "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% ifversion ghec %} +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% ifversion ghec %} - "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %}{% ifversion fpt or ghec %} - "[Understanding how {% data variables.product.prodname_dotcom %} uses and protects your data](/get-started/privacy-on-github)" {% endif %} diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md index 5f39925329..b21788de15 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md @@ -138,22 +138,18 @@ To create a new codespace, use the `gh codespace create` subcommand. gh codespace create ``` -You are prompted to choose a repository, a branch, and a machine type (if more than one is available). - -{% note %} - -**Note**: Currently, {% data variables.product.prodname_cli %} doesn't allow you to choose a dev container configuration when you create a codespace. If you want to choose a specific dev container configuration, use the {% data variables.product.prodname_dotcom %} web interface to create your codespace. For more information, click the "Web browser" tab at the top of this page. - -{% endnote %} +You are prompted to choose a repository, a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available). Alternatively, you can use flags to specify some or all of the options: ```shell -gh codespace create -r owner/repo -b branch -m machine-type +gh codespace create -r owner/repo -b branch --devcontainer-path path -m machine-type ``` In this example, replace `owner/repo` with the repository identifier. Replace `branch` with the name of the branch, or the full SHA hash of the commit, that you want to be initially checked out in the codespace. If you use the `-r` flag without the `b` flag, the codespace is created from the default branch. +Replace `path` with the path to the dev container configuration file you want to use for the new codespace. If you omit this flag and more than one dev container file is available you will be prompted to choose one from a list. For more information about the dev container configuration file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." + Replace `machine-type` with a valid identifier for an available machine type. Identifiers are strings such as: `basicLinux32gb` and `standardLinux32gb`. The type of machines that are available depends on the repository, your personal account, and your location. If you enter an invalid or unavailable machine type, the available types are shown in the error message. If you omit this flag and more than one machine type is available you will be prompted to choose one from a list. For full details of the options for this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_create). diff --git a/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md index c9ab964dbd..d270e7ba51 100644 --- a/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -17,7 +17,9 @@ topics: Every repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} comes equipped with a section for hosting documentation, called a wiki. You can use your repository's wiki to share long-form content about your project, such as how to use it, how you designed it, or its core principles. A README file quickly tells what your project can do, while you can use a wiki to provide additional documentation. For more information, see "[About READMEs](/articles/about-readmes)." -With wikis, you can write content just like everywhere else on {% data variables.product.product_name %}. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)." We use [our open-source Markup library](https://github.com/github/markup) to convert different formats into HTML, so you can choose to write in Markdown or any other supported format. +With wikis, you can write content just like everywhere else on {% data variables.product.product_name %}. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)." We use [our open-source Markup library](https://github.com/github/markup) to convert different formats into HTML, so you can choose to write in Markdown or any other supported format. + +{% data reusables.getting-started.math-and-diagrams %} {% ifversion fpt or ghes or ghec %}If you create a wiki in a public repository, the wiki is available to {% ifversion ghes %}anyone with access to {% data variables.product.product_location %}{% else %}the public{% endif %}. {% endif %}If you create a wiki in a private{% ifversion ghec or ghes %} or internal{% endif %} repository, only {% ifversion fpt or ghes or ghec %}people{% elsif ghae %}enterprise members{% endif %} with access to the repository can access the wiki. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)." diff --git a/translations/es-ES/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/translations/es-ES/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md index 8061428044..e474db0dd6 100644 --- a/translations/es-ES/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md +++ b/translations/es-ES/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md @@ -45,6 +45,11 @@ Puedes establecer un enlace a una imagen en un repositorio en {% data variables. [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]] +{% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7647 %} +## Adding mathematical expressions and diagrams{% endif %} + +{% data reusables.getting-started.math-and-diagrams %} + ## Formatos MediaWiki admitidos Independientemente del lenguaje markup en que esté escrita tu página, siempre tendrás una determinada sintaxis MediaWiki disponible. diff --git a/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index 00d8100cb1..e25796d523 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -1191,9 +1191,9 @@ Las entregas para los eventos `review_requested` y `review_request_removed` tend | `commits[][author][email]` | `secuencia` | La dirección de correo electrónico del autor de git. | | `commits[][url]` | `url` | URL que apunta al recurso de la API de la confirmación. | | `commits[][distinct]` | `boolean` | Si la confirmación es distinta de cualquier otra que se haya subido antes. | -| `commits[][added]` | `arreglo` | Un arreglo de archivos que se agregaron en la confirmación. | -| `commits[][modified]` | `arreglo` | Un areglo de archivos que modificó la confirmación. | -| `commits[][removed]` | `arreglo` | Un arreglo de archivos que se eliminaron en la confirmación. | +| `commits[][added]` | `arreglo` | Un arreglo de archivos que se agregaron en la confirmación. For extremely large commits where {% data variables.product.product_name %} is unable to calculate this list in a timely manner, this may be empty even if files were added. | +| `commits[][modified]` | `arreglo` | Un areglo de archivos que modificó la confirmación. For extremely large commits where {% data variables.product.product_name %} is unable to calculate this list in a timely manner, this may be empty even if files were modified. | +| `commits[][removed]` | `arreglo` | Un arreglo de archivos que se eliminaron en la confirmación. For extremely large commits where {% data variables.product.product_name %} is unable to calculate this list in a timely manner, this may be empty even if files were removed. | | `pusher` | `objeto` | El usuario que subió la confirmación. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} diff --git a/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md index 84ea3b7408..9ca9f69127 100644 --- a/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md @@ -33,36 +33,28 @@ Una licencia de {% data variables.product.prodname_GH_advanced_security %} propo - **Revisión de dependencias** - Muestra todo el impacto de los cambios a las dependencias y vee los detalles de las versiones vulnerables antes de que fusiones una solicitud de cambios. Para obtener más información, consulta la sección "[Acerca de la revisión de dependencias](/code-security/supply-chain-security/about-dependency-review)". -{% ifversion ghec or ghes %} +{% ifversion ghes < 3.7 or ghae %} + - **Resumen de seguridad** - Revisa la configuración de seguridad y las alertas para una organización e identifica los repositorios que tienen un riesgo mayor. Para obtener más información, consulta la sección "[Acerca del resumen de seguridad](/code-security/security-overview/about-the-security-overview)". {% endif %} {% ifversion fpt or ghec %} -La siguiente tabla resume la disponibilidad de las características de la {% data variables.product.prodname_GH_advanced_security %} para los repositorios públicos y privados. |{% ifversion fpt %} -| | Repositorio público | Repositorio privado sin {% data variables.product.prodname_advanced_security %} | Repositorio privado con {% data variables.product.prodname_advanced_security %} -|:------------------------:|:------------------------------------:|:---------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------:| -| Escaneo de código | Sí | No | Sí | -| Escaneo de secretos | Sí **(solo funcionalidad limitada)** | No | Sí | -| Revisión de dependencias | Sí | No | Sí |{% endif %} -| -{% ifversion ghec %} +La siguiente tabla resume la disponibilidad de las características de la {% data variables.product.prodname_GH_advanced_security %} para los repositorios públicos y privados. + | | Repositorio público | Repositorio privado sin {% data variables.product.prodname_advanced_security %} | Repositorio privado con {% data variables.product.prodname_advanced_security %} |:------------------------:|:------------------------------------:|:---------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------:| | Escaneo de código | Sí | No | Sí | | Escaneo de secretos | Sí **(solo funcionalidad limitada)** | No | Sí | | Revisión de dependencias | Sí | No | Sí | -| Resumen de seguridad | No | No | Sí | -{% endif %} - {% endif %} Para obtener más información sobre las características de {% data variables.product.prodname_advanced_security %} que se encuentran en desarrollo, consulta la sección "[Plan de trabajo de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap)". Para obtener un resumen de todas las características de seguridad, consulta la sección "[Características de seguridad de {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)". {% ifversion fpt or ghec %} -Las características de la {% data variables.product.prodname_GH_advanced_security %} se habilitan para todos los repositorios en {% data variables.product.prodname_dotcom_the_website %}{% ifversion ghec %}, con excepción del resumen de seguridad{% endif %}. Las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} con la {% data variables.product.prodname_advanced_security %} pueden habilitar estas características adicionalmente para repositorios privados e internos. También tienen acceso a un resumen de seguridad a nivel organziacional. {% ifversion fpt %}Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} +Las características de la {% data variables.product.prodname_GH_advanced_security %} se encuentran habilitadas para todos los repositorios públicos de {% data variables.product.prodname_dotcom_the_website %}. Las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} con la {% data variables.product.prodname_advanced_security %} pueden habilitar estas características adicionalmente para repositorios privados e internos. {% ifversion fpt %}Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} {% endif %} -{% ifversion ghes > 3.1 or ghec %} +{% ifversion ghes > 3.1 or ghec or ghae %} ## Desplegar GitHub Advanced Security en tu empresa Para aprender más sobre lo que necesitas saber para planear tu despliegue de {% data variables.product.prodname_GH_advanced_security %} en un nivel alto para revisar las fases de implementación que recomendamos, consulta la sección "[Adoptar la {% data variables.product.prodname_GH_advanced_security %} a escala](/code-security/adopting-github-advanced-security-at-scale)". diff --git a/translations/es-ES/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md b/translations/es-ES/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md index 8334e58b40..58f411623e 100644 --- a/translations/es-ES/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md +++ b/translations/es-ES/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md @@ -44,5 +44,5 @@ Cuando habilitas el uso de datos para tu repositorio privado, podrás acceder a ## Leer más - "[Acerca del uso de tus datos de {% data variables.product.prodname_dotcom %}](/articles/about-github-s-use-of-your-data)" -- "[Ver y actualizar las {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" +- "[Ver y actualizar{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" - "[Administrar la configuración de seguridad y de análisis para tu organización](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" diff --git a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md index 6e55728d0a..ee313cdf7d 100644 --- a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md +++ b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md @@ -8,7 +8,7 @@ shortTitle: Crear diagramas ## Acerca de crear diagramas -Puedes crear diagramas en lenguaje de marcado utilizando tres tipos de sintaxis diferentes: mermaid, geoJSON y topoJSON y ASCII STL. +Puedes crear diagramas en lenguaje de marcado utilizando tres tipos de sintaxis diferentes: mermaid, geoJSON y topoJSON y ASCII STL. Diagram rendering is available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, wikis, and Markdown files. ## Crear diagramas de Mermaid diff --git a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md index 8dfef46c06..e91df75990 100644 --- a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md +++ b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md @@ -6,10 +6,14 @@ versions: shortTitle: Mathematical expressions --- +## About writing mathematical expressions + To enable clear communication of mathematical expressions, {% data variables.product.product_name %} supports LaTeX formatted math within Markdown. For more information, see [LaTeX/Mathematics](http://en.wikibooks.org/wiki/LaTeX/Mathematics) in Wikibooks. {% data variables.product.company_short %}'s math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide). +Mathematical expressions rendering is available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, {% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7647 %}wikis, {% endif %}and Markdown files. + ## Writing inline expressions To include a math expression inline with your text, delimit the expression with a dollar symbol `$`. diff --git a/translations/es-ES/content/graphql/guides/forming-calls-with-graphql.md b/translations/es-ES/content/graphql/guides/forming-calls-with-graphql.md index 3e5357f32b..d18e505792 100644 --- a/translations/es-ES/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/es-ES/content/graphql/guides/forming-calls-with-graphql.md @@ -33,7 +33,6 @@ Se recomiendan los siguientes alcances: ``` repo -repo_deployment read:packages read:org read:public_key diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md index 3a956dd131..24b6a44674 100644 --- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md +++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md @@ -1,6 +1,6 @@ --- title: 'Acerca de las {% data variables.product.prodname_projects_v1 %}' -intro: '{% data variables.product.prodname_projects_v1_caps %} on {% data variables.product.product_name %} help you organize and prioritize your work. You can create {% data variables.projects.projects_v1_boards %} for specific feature work, comprehensive roadmaps, or even release checklists. Con {% data variables.product.prodname_projects_v1 %}, tienes la flexibilidad de crear flujos de trabajo personalizados que se acopñlen a tus necesidades.' +intro: 'Los {% data variables.product.prodname_projects_v1_caps %} en {% data variables.product.product_name %} te permiten organizar y priorizar tu trabajo. Puedes crear {% data variables.projects.projects_v1_boards %} para trabajo de características específicas, itinerarios integrales o incluso listas de verificación de lanzamientos. Con {% data variables.product.prodname_projects_v1 %}, tienes la flexibilidad de crear flujos de trabajo personalizados que se acopñlen a tus necesidades.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/about-project-boards - /articles/about-projects @@ -19,27 +19,27 @@ Los {% data variables.projects.projects_v1_boards_caps %} se componen de propues Las tarjetas de los {% data variables.projects.projects_v1_board_caps %} contienen metadatos relevantes para las propuestas y solicitudes de cambios, como etiquetas, asignados, el estado y quién la abrió. {% data reusables.project-management.edit-in-project %} -Puedes crear notas dentro de las columnas para que sirvan como recordatorios de tareas, referencias a las propuestas y solicitudes de cambio de cualquier repositorio en {% data variables.product.product_location %} o para agregar la información relacionada con el {% data variables.projects.projects_v1_board %}. Puedes crear una tarjeta de referencia para otro {% data variables.projects.projects_v1_board %} si agregas un enlace a una nota. Si la nota no es suficiente para tus necesidades, puedes convertirla en una propuesta. For more information on converting notes to issues, see "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)." +Puedes crear notas dentro de las columnas para que sirvan como recordatorios de tareas, referencias a las propuestas y solicitudes de cambio de cualquier repositorio en {% data variables.product.product_location %} o para agregar la información relacionada con el {% data variables.projects.projects_v1_board %}. Puedes crear una tarjeta de referencia para otro {% data variables.projects.projects_v1_board %} si agregas un enlace a una nota. Si la nota no es suficiente para tus necesidades, puedes convertirla en una propuesta. Para obtener más información sobre cómo convertir las notas en propuestas, consulta la sección "[Agregar notas a un {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)". Tipos de tableros de proyecto: -- **User-owned {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any personal repository. -- **Organization-wide {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any repository that belongs to an organization. {% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)." -- **Repository {% data variables.projects.projects_v1_board %}** are scoped to issues and pull requests within a single repository. También pueden incluir notas que hacen referencia a las propuestas y las solicitudes de extracción en otros repositorios. +- **{% data variables.projects.projects_v1_board %} perteneciente a un usuario** puede contener propuestas y solicitudes de cambio de cualquier repositorio personal. +- **{% data variables.projects.projects_v1_board %} de toda la organización** puede contener propuestas y solicitudes de cambio de cualquier repositorio que le pertenezca a una organización. {% data reusables.project-management.link-repos-to-project-board %} Para obtener más información, consulta la sección "[Enlazar un repositorio a un {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)". +- **{% data variables.projects.projects_v1_board %} de repositorio** se le da un alcance para propuestas y solicitudes de cambios dentro de un repositorio específico. También pueden incluir notas que hacen referencia a las propuestas y las solicitudes de extracción en otros repositorios. -## Creating and viewing {% data variables.projects.projects_v1_boards %} +## Crear y ver los {% data variables.projects.projects_v1_boards %} -To create a {% data variables.projects.projects_v1_board %} for your organization, you must be an organization member. Organization owners and people with {% data variables.projects.projects_v1_board %} admin permissions can customize access to the {% data variables.projects.projects_v1_board %}. +Para crear un {% data variables.projects.projects_v1_board %} de organización, debes ser miembro de ella. Los propietarios de las organizaciones y las personas con permisos administrativos de {% data variables.projects.projects_v1_board %} pueden personalizar el acceso al {% data variables.projects.projects_v1_board %}. -If an organization-owned {% data variables.projects.projects_v1_board %} includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." +Si un {% data variables.projects.projects_v1_board %} perteneciente a una organización incluye propuestas o solicitudes de cambio de un repositorio en el cual no tienes permisos de visualización, la tarjeta se redactará. Para obtener más información, consulta la sección "[Permisos de los {% data variables.product.prodname_project_v1_caps %} para una organización](/articles/project-board-permissions-for-an-organization)". -The activity view shows the {% data variables.projects.projects_v1_board %}'s recent history, such as cards someone created or moved between columns. Para acceder a la vista actividad, haz clic en **Menú** y desplázate hacia abajo. +La vista de actividad muestra el historial reciente del {% data variables.projects.projects_v1_board %}, tal como las tarjetas que haya creado alguien o movido entre columnas. Para acceder a la vista actividad, haz clic en **Menú** y desplázate hacia abajo. -To find specific cards on a {% data variables.projects.projects_v1_board %} or view a subset of the cards, you can filter {% data variables.projects.projects_v1_board %} cards. For more information, see "[Filtering cards on a {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)." +Para encontrar tarjetas específicas en un {% data variables.projects.projects_v1_board %} o vista de un subconjunto de las tarjetas, puedes filtrar las tarjetas de {% data variables.projects.projects_v1_board %}. Para obtener más información, consulta la sección "[Filtrar las tarjetas en un {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)". -To simplify your workflow and keep completed tasks off your {% data variables.projects.projects_v1_board %}, you can archive cards. For more information, see "[Archiving cards on a {% data variables.product.prodname_project_v1 %}](/articles/archiving-cards-on-a-project-board)." +Para simplificar tu flujo de trabajo y mantener las tareas completadas fuera de tu {% data variables.projects.projects_v1_board %}, puedes archivarlas. Para obtener más información, consulta la sección "[Archivar las tarjetas en un {% data variables.product.prodname_project_v1 %}](/articles/archiving-cards-on-a-project-board)". -If you've completed all of your {% data variables.projects.projects_v1_board %} tasks or no longer need to use your {% data variables.projects.projects_v1_board %}, you can close the {% data variables.projects.projects_v1_board %}. Para obtener más información, consulta la sección "[Cerrar un {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)" +Si completaste todas las tareas de tu {% data variables.projects.projects_v1_board %} o si ya no necesitas utilizar tu {% data variables.projects.projects_v1_board %}, puedes cerrar el {% data variables.projects.projects_v1_board %}. Para obtener más información, consulta la sección "[Cerrar un {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)" También puedes [inhabilitar los {% data variables.projects.projects_v1_boards %} en un repositorio](/articles/disabling-project-boards-in-a-repository) o [inhabilitar los {% data variables.projects.projects_v1_boards %} en tu organización](/articles/disabling-project-boards-in-your-organization) si prefieres rastrear tu trabajo de otra forma. @@ -68,5 +68,5 @@ Para obtener más información sobre cómo automatizar los {% data variables.pro - "[Editar un {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)"{% ifversion fpt or ghec %} - "[Copiar un {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)"{% endif %} - "[Agregar propuestas y solicitudes de cambios a un {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" -- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)" +- "[Permisos de un {% data variables.product.prodname_project_v1_caps %} para una organización](/articles/project-board-permissions-for-an-organization)" - "[Atajos del teclado](/articles/keyboard-shortcuts/#project-boards)" diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md index 2c9097c813..6c81052101 100644 --- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md +++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md @@ -19,7 +19,7 @@ allowTitleToDifferFromFilename: true {% tip %} -**Tip:** Cuando hagas a tu {% data variables.projects.projects_v1_board %} {% ifversion ghae %}interno{% else %}público{% endif %}, los miembros de la organización obtendrán acceso de lectura predeterminadamente. Puedes otorgar permisos de escritura o administración a miembros específicos de la organización si les das acceso a los equipos en los que se encuentran, agregándolos al {% data variables.projects.projects_v1_board %} como colaborador. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." +**Tip:** Cuando hagas a tu {% data variables.projects.projects_v1_board %} {% ifversion ghae %}interno{% else %}público{% endif %}, los miembros de la organización obtendrán acceso de lectura predeterminadamente. Puedes otorgar permisos de escritura o administración a miembros específicos de la organización si les das acceso a los equipos en los que se encuentran, agregándolos al {% data variables.projects.projects_v1_board %} como colaborador. Para obtener más información, consulta la sección "[Permisos de los {% data variables.product.prodname_project_v1_caps %} para una organización](/articles/project-board-permissions-for-an-organization)". {% endtip %} diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md index 6f188085ab..a33cd7330b 100644 --- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md +++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md @@ -29,4 +29,4 @@ If you reopen a {% data variables.projects.projects_v1_board %}, you have the op - "[Deleting a {% data variables.product.prodname_project_v1 %}](/articles/deleting-a-project-board)" - "[Disabling {% data variables.product.prodname_projects_v1 %} in a repository](/articles/disabling-project-boards-in-a-repository)" - "[Disabling {% data variables.product.prodname_projects_v1 %} in your organization](/articles/disabling-project-boards-in-your-organization)" -- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)" +- "[Permisos de un {% data variables.product.prodname_project_v1_caps %} para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md index 724768caa4..5975cad419 100644 --- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md +++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md @@ -1,6 +1,6 @@ --- -title: 'Configuring automation for {% data variables.product.prodname_projects_v1 %}' -intro: 'You can set up automatic workflows to move issues and pull requests to a {% data variables.projects.projects_v1_board %} column when a specified event occurs.' +title: 'Configurar la automatización para los {% data variables.product.prodname_projects_v1 %}' +intro: 'Puedes configurar flujos de trabajo automáticos para mover propuestas y solicitudes de cambio a una columna de un {% data variables.projects.projects_v1_board %} cuando ocurre un evento específico.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/configuring-automation-for-project-boards - /articles/configuring-automation-for-project-boards @@ -19,7 +19,7 @@ allowTitleToDifferFromFilename: true {% data reusables.projects.project_boards_old %} -{% data reusables.project-management.automate-project-board-permissions %} For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)." +{% data reusables.project-management.automate-project-board-permissions %} Para obtener más información, consulta la sección "[Acerca de la automatización para los {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)". {% data reusables.project-management.use-automated-template %} @@ -31,7 +31,7 @@ allowTitleToDifferFromFilename: true {% endtip %} -1. Navigate to the {% data variables.projects.projects_v1_board %} you want to automate. +1. Navega al {% data variables.projects.projects_v1_board %} que quieras automatizar. 2. En la columna que deseas automatizar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Icono Editar](/assets/images/help/projects/edit-column-button.png) 3. Haz clic en **Manage automation** (Administrar automatización). ![Botón Manage automation (Administrar automatización)](/assets/images/help/projects/manage-automation-button.png) 4. En el menú desplegable Preset (Preestablecer), selecciona el preestablecimiento de la automatización. ![Selecciona preestablecer la automatización desde el menú](/assets/images/help/projects/select-automation.png) @@ -39,4 +39,4 @@ allowTitleToDifferFromFilename: true 6. Haz clic en **Update automation** (Actualizar automatización). ## Leer más -- "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)" +- "[Acerca de la automatización para los {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)" diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md index 3f52196fdb..6831e7c6f7 100644 --- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md +++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md @@ -1,6 +1,6 @@ --- title: 'Crear una {% data variables.product.prodname_project_v1 %}' -intro: '{% data variables.projects.projects_v1_boards_caps %} can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.' +intro: 'Los {% data variables.projects.projects_v1_boards_caps %} pueden utilizarse para crear flujos de trabajo personalizados que se acoplen a tus necesidades, como rastrear y priorizar el trabajo de características específicas, itinerarios integrales o incluso listas de verificación.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/creating-a-project-board - /articles/creating-a-project @@ -23,15 +23,15 @@ allowTitleToDifferFromFilename: true {% data reusables.project-management.copy-project-boards %} -{% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %} ](/articles/linking-a-repository-to-a-project-board)." +{% data reusables.project-management.link-repos-to-project-board %} Para obtener más información, consulta la sección "[Enlazar un repositorio a un {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)". -Once you've created your {% data variables.projects.projects_v1_board %}, you can add issues, pull requests, and notes to it. For more information, see "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" and "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)." +Una vez que hayas creado tu {% data variables.projects.projects_v1_board %}, puedes agregar propuestas, solicitudes de cambio y notas a este. Para obtener más información, consulta la sección "[Agregar propuestas y solicitudes de cambio a un {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" y "[Agregar notas a un {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)". -You can also configure workflow automations to keep your {% data variables.projects.projects_v1_board %} in sync with the status of issues and pull requests. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)." +También puedes configurar automatizaciones de flujo de trabajo para mantener sincronizado a tu {% data variables.projects.projects_v1_board %} con el estado de las propuestas y solicitudes de cambios. Para obtener más información, consulta la sección "[Acerca de la automatización para los {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)". {% data reusables.project-management.project-board-import-with-api %} -## Creating a user-owned {% data variables.projects.projects_v1_board %} +## Crear un {% data variables.projects.projects_v1_board %} perteneciente a un usuario {% data reusables.projects.classic-project-creation %} @@ -53,7 +53,7 @@ You can also configure workflow automations to keep your {% data variables.proje {% data reusables.project-management.edit-project-columns %} -## Creating an organization-wide {% data variables.projects.projects_v1_board %} +## Crear un {% data variables.projects.projects_v1_board %} de toda la organización {% data reusables.projects.classic-project-creation %} @@ -76,7 +76,7 @@ You can also configure workflow automations to keep your {% data variables.proje {% data reusables.project-management.edit-project-columns %} -## Creating a repository {% data variables.projects.projects_v1_board %} +## Crear un {% data variables.projects.projects_v1_board %} de un repositorio {% data reusables.projects.classic-project-creation %} diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md index 424c2cd6f3..e33789461f 100644 --- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md +++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md @@ -1,7 +1,7 @@ --- title: 'Administrar las {% data variables.product.prodname_projects_v1 %}' shortTitle: 'Administrar las {% data variables.product.prodname_projects_v1 %}' -intro: 'Learn how to create and manage {% data variables.projects.projects_v1_boards %}' +intro: 'Aprende cómo crear y administrar los {% data variables.projects.projects_v1_boards %}' versions: feature: projects-v1 topics: diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md index 7e6ff1abbe..32d31c2451 100644 --- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md +++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md @@ -1,6 +1,6 @@ --- -title: 'Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}' -intro: 'You can add issues and pull requests to a {% data variables.projects.projects_v1_board %} in the form of cards and triage them into columns.' +title: 'Agregar propuestas y solicitudes de cambio a un {% data variables.product.prodname_project_v1 %}' +intro: 'Puedes agregar propuestas y solicitudes de cambio a un {% data variables.projects.projects_v1_board %} en forma de tarjetas y clasificarlas en columnas.' redirect_from: - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board - /articles/adding-issues-and-pull-requests-to-a-project @@ -10,16 +10,16 @@ versions: feature: projects-v1 topics: - Pull requests -shortTitle: 'Add issues & PRs to {% data variables.product.prodname_project_v1 %}' +shortTitle: 'Agregar propuestas & solicitudes de cambio a un {% data variables.product.prodname_project_v1 %}' allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} -You can add issue or pull request cards to your {% data variables.projects.projects_v1_board %} by: +Puedes agregar tarjetas de propuestas o solicitudes de cambio a tu {% data variables.projects.projects_v1_board %} al: - Arrastrar tarjetas desde la sección **Triage** (Jerarquizar) en la barra lateral. - Escribir la propuesta o URL de solicitud de extracción en una tarjeta. -- Searching for issues or pull requests in the {% data variables.projects.projects_v1_board %} search sidebar. +- Buscar propuestas o solicitudes de cambios en la barra lateral de búsqueda del {% data variables.projects.projects_v1_board %}. Puedes poner un máximo de 2500 tarjetas en cada columna del proyecto. Si una columna ha alcanzado un número máximo de tarjetas, ninguna tarjeta puede moverse a esa columna. @@ -27,28 +27,28 @@ Puedes poner un máximo de 2500 tarjetas en cada columna del proyecto. Si una co {% note %} -**Note:** You can also add notes to your project board to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_name %}, or to add related information to your {% data variables.projects.projects_v1_board %}. Para obtener más información, consulta "[Agregar notas a un tablero de proyecto](/articles/adding-notes-to-a-project-board)". +**Nota:** También puedes agregar notas a tu tablero de proyecto para que sirvan como recordatorios de las tareas, referencias a las propuestas y solicitudes de cambios de cualquier repositorio en {% data variables.product.product_name %} o para agregar información relacionada a tu {% data variables.projects.projects_v1_board %}. Para obtener más información, consulta "[Agregar notas a un tablero de proyecto](/articles/adding-notes-to-a-project-board)". {% endnote %} {% data reusables.project-management.edit-in-project %} -{% data reusables.project-management.link-repos-to-project-board %} When you search for issues and pull requests to add to your {% data variables.projects.projects_v1_board %}, the search automatically scopes to your linked repositories. Puedes eliminar estos calificadores para buscar dentro de todos los repositorios de la organización. Para obtener más información, consulta "[Vincular un repositorio con un tablero de proyecto](/articles/linking-a-repository-to-a-project-board)". +{% data reusables.project-management.link-repos-to-project-board %} Cuando buscas propuestas y solicitudes de cambio para agregarlas a tu {% data variables.projects.projects_v1_board %}, la búsqueda toma automáticamente el alcance de tus repositorios enlazados. Puedes eliminar estos calificadores para buscar dentro de todos los repositorios de la organización. Para obtener más información, consulta "[Vincular un repositorio con un tablero de proyecto](/articles/linking-a-repository-to-a-project-board)". -## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %} +## Agregar propuestas y solicitudes de cambio a un {% data variables.projects.projects_v1_board %} -1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to add issues and pull requests. -2. In your {% data variables.projects.projects_v1_board %}, click {% octicon "plus" aria-label="The plus icon" %} **Add cards**. ![Agregar botón de tarjetas](/assets/images/help/projects/add-cards-button.png) -3. Search for issues and pull requests to add to your {% data variables.projects.projects_v1_board %} using search qualifiers. Para más información sobre la búsqueda de calificadores que puedes usar, consulta "[Buscar propuestas](/articles/searching-issues)". ![Buscar propuestas y solicitudes de extracción](/assets/images/help/issues/issues_search_bar.png) +1. Navega al {% data variables.projects.projects_v1_board %} en donde quieres agregar propuestas y solicitudes de cambio. +2. En tu {% data variables.projects.projects_v1_board %}, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Agregar tarjetas**. ![Agregar botón de tarjetas](/assets/images/help/projects/add-cards-button.png) +3. Busca las propuestas y solicitudes de cambio para agregar a tu {% data variables.projects.projects_v1_board %} utilizando los calificadores de búsqueda. Para más información sobre la búsqueda de calificadores que puedes usar, consulta "[Buscar propuestas](/articles/searching-issues)". ![Buscar propuestas y solicitudes de extracción](/assets/images/help/issues/issues_search_bar.png) {% tip %} **Tips:** - También puedes agregar una propuesta o solicitud de extracción al escribir la URL en una tarjeta. - - If you're working on a specific feature, you can apply a label to each related issue or pull request for that feature, and then easily add cards to your {% data variables.projects.projects_v1_board %} by searching for the label name. Para obtener más información, consulta "[Aplicar etiquetas a propuestas y solicitudes de extracción](/articles/applying-labels-to-issues-and-pull-requests)". + - Si estás trabajando en una característica específica, puedes aplicar una etiqueta a cada propuesta o solicitud de cambios relacionada para esta y luego agregar tarjetas fácilmente a tu {% data variables.projects.projects_v1_board %} buscando el nombre de la etiqueta. Para obtener más información, consulta "[Aplicar etiquetas a propuestas y solicitudes de extracción](/articles/applying-labels-to-issues-and-pull-requests)". {% endtip %} -4. From the filtered list of issues and pull requests, drag the card you'd like to add to your {% data variables.projects.projects_v1_board %} and drop it in the correct column. Como alternativa, puedes mover las tarjetas usando los atajos del teclado. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} +4. Desde la lista filtrada de propuestas y solicitudes de cambio, arrastra la tarjeta que te gustaría agregar a tu {% data variables.projects.projects_v1_board %} y suéltala en la columna correcta. Como alternativa, puedes mover las tarjetas usando los atajos del teclado. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} {% tip %} @@ -56,16 +56,16 @@ Puedes poner un máximo de 2500 tarjetas en cada columna del proyecto. Si una co {% endtip %} -## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %} from the sidebar +## Agregar propuestas y solicitudes de cambio a un {% data variables.projects.projects_v1_board %} desde la barra lateral 1. En el lateral derecho de una propuesta o solicitud de extracción, haz clic en **Projects{% octicon "gear" aria-label="The Gear icon" %} (Proyectos**. ![Botón del tablero de proyecto en la barra lateral](/assets/images/help/projects/sidebar-project.png) -2. Click the **Recent**, **Repository**,**User**, or **Organization** tab for the {% data variables.projects.projects_v1_board %} you would like to add to. ![Pestañas Recent (Reciente), Repository (Repositorio) y Organization (Organización)](/assets/images/help/projects/sidebar-project-tabs.png) +2. Haz clic en la pestaña de **Reciente**, **Repositorio**, **Usuario** u **Organización** del {% data variables.projects.projects_v1_board %} al que te gustaría agregarlas. ![Pestañas Recent (Reciente), Repository (Repositorio) y Organization (Organización)](/assets/images/help/projects/sidebar-project-tabs.png) 3. Escribe el nombre del proyecto en el campo **Filter projects** (Filtrar proyectos). ![Cuadro de búsqueda del tablero de proyecto](/assets/images/help/projects/sidebar-search-project.png) -4. Select one or more {% data variables.projects.projects_v1_boards %} where you want to add the issue or pull request. ![Tablero de proyecto seleccionado](/assets/images/help/projects/sidebar-select-project.png) -5. Haz clic en {% octicon "triangle-down" aria-label="The down triangle icon" %}, luego haz clic en la columna en la que quieras colocar tu propuesta o solicitud de extracción. The card will move to the bottom of the {% data variables.projects.projects_v1_board %} column you select. ![Menú Move card to column (Mover tarjeta a la columna)](/assets/images/help/projects/sidebar-select-project-board-column-menu.png) +4. Selecciona uno o más {% data variables.projects.projects_v1_boards %} a los que te gustaría agregar la propuesta o solicitud de cambios. ![Tablero de proyecto seleccionado](/assets/images/help/projects/sidebar-select-project.png) +5. Haz clic en {% octicon "triangle-down" aria-label="The down triangle icon" %}, luego haz clic en la columna en la que quieras colocar tu propuesta o solicitud de extracción. La tarjeta se moverá a la parte inferior de la columna del {% data variables.projects.projects_v1_board %} que selecciones. ![Menú Move card to column (Mover tarjeta a la columna)](/assets/images/help/projects/sidebar-select-project-board-column-menu.png) ## Leer más - "[Acerca de {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)" -- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)" -- "[Filtering cards on a {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)" +- "[Editar un {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)" +- "[Filtrar las tarjetas en un {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)" diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md index 3e10bff729..d6a5f2e596 100644 --- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md +++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md @@ -56,10 +56,10 @@ Cuando conviertes una nota en una propuesta, la propuesta se crea automáticamen 1. Desplázate hasta la nota que deseas convertir en propuesta. {% data reusables.project-management.project-note-more-options %} 3. Haz clic en **Convert to issue** (Convertir en propuesta). ![Botón para convertir en propuesta](/assets/images/help/projects/convert-to-issue.png) -4. If the card is on an organization-wide {% data variables.projects.projects_v1_board %}, in the drop-down menu, choose the repository you want to add the issue to. ![Menú desplegable enumerando los repositorios donde puedes crear la propuesta](/assets/images/help/projects/convert-note-choose-repository.png) +4. Si la tarjeta está en un {% data variables.projects.projects_v1_board %} de toda la organización, en el menú desplegable, elige el repositorio al cual quieras agregar la propuesta. ![Menú desplegable enumerando los repositorios donde puedes crear la propuesta](/assets/images/help/projects/convert-note-choose-repository.png) 5. Opcionalmente, edita el título de la propuesta completada previamente, y escribe el cuerpo de la propuesta. ![Campos para título y cuerpo de la propuesta](/assets/images/help/projects/convert-note-issue-title-body.png) 6. Haz clic en **Convert to issue** (Convertir en propuesta). -7. La nota se convertirá automáticamente en una propuesta. In the {% data variables.projects.projects_v1_board %}, the new issue card will be in the same location as the previous note. +7. La nota se convertirá automáticamente en una propuesta. En el {% data variables.projects.projects_v1_board %}, la tarjeta de propuesta nueva estará en la misma ubicación que la nota previa. ## Editar o eliminar una nota @@ -72,5 +72,5 @@ Cuando conviertes una nota en una propuesta, la propuesta se crea automáticamen - "[Acerca de {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)" - "[Crear un {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)" -- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)" +- "[Editar un {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)" - "[Agregar propuestas y solicitudes de cambios a un {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md index 3bc2d5c17e..c28cf7a66e 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md @@ -95,20 +95,20 @@ A continuación se encuentra un ejemplo de una etiqueta de `front-end` que cream {% ifversion projects-v2 %} -You can use {% data variables.projects.projects_v2 %} on {% data variables.product.prodname_dotcom %} to plan and track the work for your team. Un proyecto es una hoja de cálculo personalizada que se integra con tus propuestas y solicitudes de cambvios en {% data variables.product.prodname_dotcom %} y que se actualiza automáticamente con la información de {% data variables.product.prodname_dotcom %}. Puedes personalziar el diseño si filtras, clasificas y agrupas tus propuestas y solicitudes de cambios. To get started with projects, see "[Quickstart for projects](/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects)." -### Project example +Puedes utilizar {% data variables.projects.projects_v2 %} en {% data variables.product.prodname_dotcom %} para planear y rastrear el trabajo para tu equipo. Un proyecto es una hoja de cálculo personalizada que se integra con tus propuestas y solicitudes de cambvios en {% data variables.product.prodname_dotcom %} y que se actualiza automáticamente con la información de {% data variables.product.prodname_dotcom %}. Puedes personalziar el diseño si filtras, clasificas y agrupas tus propuestas y solicitudes de cambios. Para iniciar con los proyectos, consulta la sección "[Inicio rápido para los proyectos](/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects)". +### Ejemplo de proyecto Aquí tienes el diseño de tabla de un proyecto ejemplo, la cual se llenó con propuestas del proyecto Octocat que hemos creado. -![Projects table layout example](/assets/images/help/issues/quickstart-projects-table-view.png) +![Ejemplo de diseño de la tabla de proyectos](/assets/images/help/issues/quickstart-projects-table-view.png) También podemos ver el mismo proyecto como un tablero. -![Projects board layout example](/assets/images/help/issues/quickstart-projects-board-view.png) +![Ejemplo de diseño del tablero de proyectos](/assets/images/help/issues/quickstart-projects-board-view.png) {% endif %} {% ifversion projects-v1 %} -You can {% ifversion projects-v2 %} also use the existing{% else %} use{% endif %} {% data variables.product.prodname_projects_v1 %} on {% data variables.product.prodname_dotcom %} to plan and track your or your team's work. Los tableros de proyecto están compuestos por propuestas, solicitudes de extracción y notas que se categorizan como tarjetas en columnas a tu elección. Puedes crear tableros de proyecto para presentar trabajo, planes de alto nivel o incluso listas de verificación. Para obtener más información, consulta "[Acerca de los tableros de proyectos](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." +Puedes {% ifversion projects-v2 %} utilizar el {% else %} utilizar {% endif %} {% data variables.product.prodname_projects_v1 %} en {% data variables.product.prodname_dotcom %} para planear y rastrear tu trabajo o el de tu equipo. Los tableros de proyecto están compuestos por propuestas, solicitudes de extracción y notas que se categorizan como tarjetas en columnas a tu elección. Puedes crear tableros de proyecto para presentar trabajo, planes de alto nivel o incluso listas de verificación. Para obtener más información, consulta "[Acerca de los tableros de proyectos](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." ### Ejemplo del trablero de proyecto A continuación, se presenta un tablero de proyecto para nuestro ejemplo del Proyecto Octocat, con la propuesta que creamos y las propuestas más pequeñas en las que lo dividimos agregadas a este. @@ -125,6 +125,6 @@ Ya aprendiste sobre las herramientas que ofrece {% data variables.product.prodna - "[Acerca de las propuestas y solicitudes de cambios](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)" para aprender más sobre las plantillas de propuestas - "[Administrar etiquetas](/issues/using-labels-and-milestones-to-track-work/managing-labels)" para aprender cómo crear, editar y borrar etiquetas - "[Acerca de las listas de tareas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)" para aprender más sobre las tareas -{% ifversion projects-v2 %} - "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)" for learning more about projects -- "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)" for learning how to customize views for projects{% endif %} -{% ifversion projects-v1 %}- "[About {% data variables.product.prodname_projects_v1 %}](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)" for learning how to manage project boards{% endif %} +{% ifversion projects-v2 %} - "[Acerca de los proyectos](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)" para aprender más sobre los proyectos +- "[Personalizar una vista](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)" para aprender cómo personalizar las vistas para los proyectos{% endif %} +{% ifversion projects-v1 %}- "[Acerca de los {% data variables.product.prodname_projects_v1 %}](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)" para aprender cómo manejar los tableros de proyecto{% endif %} diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/quickstart.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/quickstart.md index bd552a64fd..a415d8389e 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/quickstart.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/quickstart.md @@ -97,5 +97,5 @@ Puedes utilizar las propuestas para una amplia gama de propósitos. Por ejemplo: Aquí tienes algunos recursos útiles para que tomes tus siguientes pasos con {% data variables.product.prodname_github_issues %}: - Para aprender más sobre las propuestas, consulta la sección "[Acerca de las propuestas](/issues/tracking-your-work-with-issues/about-issues)". -- To learn more about how projects can help you with planning and tracking, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."{% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %} +- Para aprender más sobre cómo pueden ayudarte los proyectos con la planeación y el rastreo, consulta la sección {% ifversion projects-v2 %}"[Acerca de los proyectos](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)".{% else %}"[Organizar tu trabajo con los tableros de proyecto](/issues/organizing-your-work-with-project-boards)".{% endif %} - Para aprender más sobre cómo utilizar las plantillas de propuestas{% ifversion fpt or ghec %} y emitir formatos{% endif %} para motivar a los contribuyentes a proporcionar información específica, consulta la sección "[Utilizar las plantillas para motivar las propuestas y solicitudes de cambios útiles](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)". diff --git a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md index a02e2610c9..891bdc1957 100644 --- a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md +++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md @@ -15,19 +15,19 @@ shortTitle: Personalizar el perfil de una organización ## Acerca de la página de perfil de la organización {% ifversion org-profile-pin-private %} -You can customize your organization's Overview page to show a README and pinned repositories dedicated to public users or members of the organization. +Puedes personalizar la página de resumen de tu organización para que muestre un README y los repositorios fijados y dedicados a los usuarios públicos o a los miembros de la organización. -![Image of a public organization profile page](/assets/images/help/organizations/public_profile.png) +![Imagen de una página de perfil de organización pública](/assets/images/help/organizations/public_profile.png) -Members of your organization who are signed into {% data variables.product.prodname_dotcom %}, can select a `member` or `public` view of the README and pinned repositories when they visit your organization's profile page. +Los miembros de tu organización que iniciaron sesión en {% data variables.product.prodname_dotcom %} pueden seleccionar una vista de `member` o `public` del README y los repositorios fijos cuando visiten la página de perfil de tu organización. -![Image of a public organization profile page view context switcher](/assets/images/help/organizations/profile_view_switcher_public.png) +![Imagen del cambiador de contexto de vista para una página de perfil de una organización pública](/assets/images/help/organizations/profile_view_switcher_public.png) -The view defaults to `member` if either a members-only README or members-only pinned repositories are present, and `public` otherwise. +La vista está predeterminada a `member` si están presente s ya sea un README o los repositorios exclusivos para miembros y, de lo contrario, será `public`. -![Image of a members only organization profile page](/assets/images/help/organizations/member_only_profile.png) +![Imagen de una página de perfil de una organización exclusiva para miembros](/assets/images/help/organizations/member_only_profile.png) -Users who are not members of your organization will be shown a `public` view. +Los usuarios que no sean miembros de tu organización tendrán una vista de `public`. ### Repositorios anclados @@ -64,7 +64,7 @@ Puedes formatear el texto e incluir emojis, imágenes y GIFs en el README del pe 2. En el repositorio `.github-private` de tu organización, crea un archivo `README.md` en la carpeta `profile`. 3. Confirma los cambios al archivo `README.md`. El contenido del `README.md` se mostrará en la vista de miembros del perfil de tu organización. - ![Image of an organization's member-only README](/assets/images/help/organizations/org_member_readme.png) + ![Imagen de un README de una organización exclusiva para miembros](/assets/images/help/organizations/org_member_readme.png) ## Fijar repositorios a tu perfil de organización diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/index.md index 151b332f3b..c591323938 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/index.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/index.md @@ -1,6 +1,6 @@ --- -title: 'Managing access to your organization’s {% data variables.product.prodname_projects_v1 %}' -intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give organization members, teams, and outside collaborators different levels of access to {% data variables.projects.projects_v1_boards %} owned by your organization.' +title: 'Administrar el acceso al {% data variables.product.prodname_projects_v1 %} de tu organización' +intro: 'Como propietario de una organización o administrador de un {% data variables.projects.projects_v1_board %}, puedes proporcionar a los miembros, equipos y colaboradores externos de una organización niveles diferentes de acceso a los {% data variables.projects.projects_v1_boards %} que pertenecen a ella.' redirect_from: - /articles/managing-access-to-your-organization-s-project-boards - /articles/managing-access-to-your-organizations-project-boards @@ -20,7 +20,7 @@ children: - /managing-an-individuals-access-to-an-organization-project-board - /adding-an-outside-collaborator-to-a-project-board-in-your-organization - /removing-an-outside-collaborator-from-an-organization-project-board -shortTitle: 'Manage {% data variables.product.prodname_project_v1 %} access' +shortTitle: 'Administrar el acceso a {% data variables.product.prodname_project_v1 %}' allowTitleToDifferFromFilename: true --- diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md index 403c1203c4..0738ecd87f 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md @@ -42,4 +42,4 @@ Predeterminadamente, los miembros de las organizaciones tienen acceso de escritu - "[Administrar el acceso de un individuo al {% data variables.product.prodname_project_v1 %} de una organización](/articles/managing-an-individual-s-access-to-an-organization-project-board)" - "[Administrar el acceso del equipo al {% data variables.product.prodname_project_v1 %} de una organización](/articles/managing-team-access-to-an-organization-project-board)" -- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)" +- "[Permisos de un {% data variables.product.prodname_project_v1_caps %} para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md index 455b32dfe9..defcf410a5 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md @@ -1,6 +1,6 @@ --- -title: 'Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}' -intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can manage an individual member''s access to a {% data variables.projects.projects_v1_board %} owned by your organization.' +title: 'Administrar el acceso de un individuo al {% data variables.product.prodname_project_v1 %} de una organización' +intro: 'Como propietario de una organización o administrador de un {% data variables.projects.projects_v1_board %}, puedes administrar el acceso individual de un miembro a un {% data variables.projects.projects_v1_board %} que le pertenezca a tu organización.' redirect_from: - /articles/managing-an-individual-s-access-to-an-organization-project-board - /articles/managing-an-individuals-access-to-an-organization-project-board @@ -21,11 +21,11 @@ allowTitleToDifferFromFilename: true {% note %} -**Note:** {% data reusables.project-management.cascading-permissions %} For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." +**Nota:** {% data reusables.project-management.cascading-permissions %} Para obtener más información, consulta la sección "[Permisos de {% data variables.product.prodname_project_v1_caps %} para una organización](/articles/project-board-permissions-for-an-organization)". {% endnote %} -## Giving an organization member access to a {% data variables.projects.projects_v1_board %} +## Proporcionar a un miembro de la organización acceso a un {% data variables.projects.projects_v1_board %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} @@ -39,7 +39,7 @@ allowTitleToDifferFromFilename: true {% data reusables.project-management.add-collaborator %} {% data reusables.project-management.collaborator-permissions %} -## Changing an organization member's access to a {% data variables.projects.projects_v1_board %} +## Cambiar el acceso de un miembro de una organización a un {% data variables.projects.projects_v1_board %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} @@ -51,9 +51,9 @@ allowTitleToDifferFromFilename: true {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.collaborator-permissions %} -## Removing an organization member's access to a {% data variables.projects.projects_v1_board %} +## Eliminar el acceso de un miembro de una organización para un {% data variables.projects.projects_v1_board %} -When you remove a collaborator from a {% data variables.projects.projects_v1_board %}, they may still retain access to the board based on the permissions they have for other roles. To completely remove access to a {% data variables.projects.projects_v1_board %}, you must remove access for each role the person has. For instance, a person may have access to the {% data variables.projects.projects_v1_board %} as an organization member or team member. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." +Cuando eliminas a un colaborador de un {% data variables.projects.projects_v1_board %}, aún podrían retener el acceso al tablero con base en los permisos que tengan para otros roles. Para eliminar el acceso a un {% data variables.projects.projects_v1_board %} completamente, debes eliminar el acceso para cada rol que tenga la persona. Por ejemplo, una persona podría tener acceso al {% data variables.projects.projects_v1_board %} como miembro de una organización o de un equipo. Para obtener más información, consulta la sección "[Permisos de los {% data variables.product.prodname_project_v1_caps %} para una organización](/articles/project-board-permissions-for-an-organization)". {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} @@ -67,4 +67,4 @@ When you remove a collaborator from a {% data variables.projects.projects_v1_boa ## Leer más -- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)" +- "[Permisos de un {% data variables.product.prodname_project_v1_caps %} para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md index 32d6f9ca5f..e31aa210dc 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md @@ -1,6 +1,6 @@ --- -title: 'Managing team access to an organization {% data variables.product.prodname_project_v1 %}' -intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give a team access to a {% data variables.projects.projects_v1_board %} owned by your organization.' +title: 'Administrar el acceso de un equipo al {% data variables.product.prodname_project_v1 %} de una organización' +intro: 'Como propietario de organización o administrador de {% data variables.projects.projects_v1_board %}, puedes dar acceso a un equipo para un {% data variables.projects.projects_v1_board %} que le pertenezca a tu organización.' redirect_from: - /articles/managing-team-access-to-an-organization-project-board - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board @@ -21,8 +21,8 @@ allowTitleToDifferFromFilename: true {% warning %} **Advertencias:** -- You can change a team's permission level if the team has direct access to a {% data variables.projects.projects_v1_board %}. If the team's access to the {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %}. -- If you add or remove {% data variables.projects.projects_v1_board %} access for a parent team, each of that parent's child teams will also receive or lose access to the {% data variables.projects.projects_v1_board %}. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)". +- Puedes cambiar el nivel de permiso de un equipo si este tiene acceso directo a un {% data variables.projects.projects_v1_board %}. Si el acceso de un equipo al {% data variables.projects.projects_v1_board %} se hereda de un equipo padre, debes cambiar el acceso de dicho equipo padre al {% data variables.projects.projects_v1_board %}. +- Si agregas o eliminas el acceso a un {% data variables.projects.projects_v1_board %} para un equipo padre, cada uno de los equipos hijos de este también recibirán o perderán el acceso al {% data variables.projects.projects_v1_board %}. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)". {% endwarning %} diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md index ec5085c914..2473e39d6e 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md @@ -1,6 +1,6 @@ --- -title: 'Removing an outside collaborator from an organization {% data variables.product.prodname_project_v1 %}' -intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can remove an outside collaborator''s access to a {% data variables.projects.projects_v1_board %}.' +title: 'Eliminar a un colaborador externo del {% data variables.product.prodname_project_v1 %} de una organización' +intro: 'Como propietario de una organización o administrador de un {% data variables.projects.projects_v1_board %}, puedes eliminar el acceso de un colaborador externo a un {% data variables.projects.projects_v1_board %}.' redirect_from: - /articles/removing-an-outside-collaborator-from-an-organization-project-board - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index 9017551439..47112b17da 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -63,89 +63,89 @@ Some of the features listed below are limited to organizations using {% data var | Repository action | Read | Triage | Write | Maintain | Admin | |:---|:---:|:---:|:---:|:---:|:---:| -| Manage [individual](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository), and [outside collaborator](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) access to the repository | | | | | **X** | -| Pull from the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Fork the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Edit and delete their own comments | **X** | **X** | **X** | **X** | **X** | -| Open issues | **X** | **X** | **X** | **X** | **X** | -| Close issues they opened themselves | **X** | **X** | **X** | **X** | **X** | -| Reopen issues they closed themselves | **X** | **X** | **X** | **X** | **X** | -| Have an issue assigned to them | **X** | **X** | **X** | **X** | **X** | -| Send pull requests from forks of the team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Submit reviews on pull requests | **X** | **X** | **X** | **X** | **X** | -| View published releases | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| Edit wikis in public repositories | **X** | **X** | **X** | **X** | **X** | -| Edit wikis in private repositories | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| [Report abusive or spammy content](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| Apply/dismiss labels | | **X** | **X** | **X** | **X** | -| Create, edit, delete labels | | | **X** | **X** | **X** | -| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** | -| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** | -| Apply milestones | | **X** | **X** | **X** | **X** | -| Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests)| | **X** | **X** | **X** | **X** | -| Request [pull request reviews](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | -| Push to (write) the person or team's assigned repositories | | | **X** | **X** | **X** | -| Edit and delete anyone's comments on commits, pull requests, and issues | | | **X** | **X** | **X** | -| [Hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Lock conversations](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | -| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) | | | **X** | **X** | **X** | -| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [Mark a draft pull request as ready for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| [Convert a pull request to a draft](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** | -| [Apply suggested changes](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** | -| Create [status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} -| Create and edit releases | | | **X** | **X** | **X** | -| View draft releases | | | **X** | **X** | **X** | -| Edit a repository's description | | | | **X** | **X** |{% ifversion fpt or ghae or ghec %} -| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package) | | | | | **X** | {% endif %} -| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Enable wikis and restrict wiki editors | | | | **X** | **X** | -| Enable project boards | | | | **X** | **X** | -| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [Manage branch protection rules](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **X** | -| [Push to protected branches](/articles/about-protected-branches) | | | | **X** | **X** | -| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **X** |{% ifversion fpt or ghes > 3.4 or ghae-issue-6337 or ghec %} -| Create tags that match a [tag protection rule](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | **X** | **X** | -| Delete tags that match a [tag protection rule](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | | **X** |{% endif %} -| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt or ghec %} -| Limit [interactions in a repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)| | | | **X** | **X** |{% endif %} -| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **X** | -| [Define code owners for a repository](/articles/about-code-owners) | | | | | **X** | -| Add a repository to a team (see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **X** | -| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **X** | -| Change a repository's settings | | | | | **X** | -| Manage team and collaborator access to the repository | | | | | **X** | -| Edit the repository's default branch | | | | | **X** | -| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | -| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** | -| Manage webhooks and deploy keys | | | | | **X** |{% ifversion fpt or ghec %} -| [Manage data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository) | | | | | **X** |{% endif %} -| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [Archive repositories](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt or ghec %} -| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** |{% endif %} -| Create autolink references to external resources, like Jira or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion discussions %} -| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | -| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | -| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions) to a new repository| | | **X** | **X** | **X** | -| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | -| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **X** | | **X** | **X** |{% endif %}{% ifversion fpt or ghec %} -| Create [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** |{% endif %} +| Manage [individual](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository), and [outside collaborator](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) access to the repository | | | | | **✔️** | +| Pull from the person or team's assigned repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Fork the person or team's assigned repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Edit and delete their own comments | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Open issues | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Close issues they opened themselves | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Reopen issues they closed themselves | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Have an issue assigned to them | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Send pull requests from forks of the team's assigned repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Submit reviews on pull requests | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| View published releases | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %} +| Edit wikis in public repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Edit wikis in private repositories | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| [Report abusive or spammy content](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %} +| Apply/dismiss labels | | **✔️** | **✔️** | **✔️** | **✔️** | +| Create, edit, delete labels | | | **✔️** | **✔️** | **✔️** | +| Close, reopen, and assign all issues and pull requests | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **✔️** | **✔️** | **✔️** | +| Apply milestones | | **✔️** | **✔️** | **✔️** | **✔️** | +| Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests)| | **✔️** | **✔️** | **✔️** | **✔️** | +| Request [pull request reviews](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **✔️** | **✔️** | **✔️** | **✔️** | +| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **✔️** | **✔️** | **✔️** | +| Push to (write) the person or team's assigned repositories | | | **✔️** | **✔️** | **✔️** | +| Edit and delete anyone's comments on commits, pull requests, and issues | | | **✔️** | **✔️** | **✔️** | +| [Hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **✔️** | **✔️** | **✔️** | +| [Lock conversations](/communities/moderating-comments-and-conversations/locking-conversations) | | | **✔️** | **✔️** | **✔️** | +| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) | | | **✔️** | **✔️** | **✔️** | +| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **✔️** | **✔️** | **✔️** | +| [Mark a draft pull request as ready for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | +| [Convert a pull request to a draft](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | +| Submit reviews that affect a pull request's mergeability | | | **✔️** | **✔️** | **✔️** | +| [Apply suggested changes](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) to pull requests | | | **✔️** | **✔️** | **✔️** | +| Create [status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **✔️** | **✔️** | **✔️** |{% endif %} +| Create and edit releases | | | **✔️** | **✔️** | **✔️** | +| View draft releases | | | **✔️** | **✔️** | **✔️** | +| Edit a repository's description | | | | **✔️** | **✔️** |{% ifversion fpt or ghae or ghec %} +| [View and install packages](/packages/publishing-and-managing-packages) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **✔️** | **✔️** | **✔️** | +| [Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package) | | | | | **✔️** | {% endif %} +| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **✔️** | **✔️** | +| Enable wikis and restrict wiki editors | | | | **✔️** | **✔️** | +| Enable project boards | | | | **✔️** | **✔️** | +| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **✔️** | **✔️** | +| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **✔️** | **✔️** | +| [Manage branch protection rules](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **✔️** | +| [Push to protected branches](/articles/about-protected-branches) | | | | **✔️** | **✔️** | +| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **✔️** |{% ifversion fpt or ghes > 3.4 or ghae-issue-6337 or ghec %} +| Create tags that match a [tag protection rule](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | **✔️** | **✔️** | +| Delete tags that match a [tag protection rule](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | | **✔️** |{% endif %} +| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| Limit [interactions in a repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)| | | | **✔️** | **✔️** |{% endif %} +| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **✔️** | +| [Define code owners for a repository](/articles/about-code-owners) | | | | | **✔️** | +| Add a repository to a team (see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **✔️** | +| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **✔️** | +| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **✔️** | +| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **✔️** | +| Change a repository's settings | | | | | **✔️** | +| Manage team and collaborator access to the repository | | | | | **✔️** | +| Edit the repository's default branch | | | | | **✔️** | +| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **✔️** | +| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **✔️** | **✔️** | **✔️** | +| Manage webhooks and deploy keys | | | | | **✔️** |{% ifversion fpt or ghec %} +| [Manage data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository) | | | | | **✔️** |{% endif %} +| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **✔️** | +| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **✔️** | +| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **✔️** | +| [Archive repositories](/articles/about-archiving-repositories) | | | | | **✔️** |{% ifversion fpt or ghec %} +| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **✔️** |{% endif %} +| Create autolink references to external resources, like Jira or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **✔️** |{% ifversion discussions %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **✔️** | **✔️** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) for {% data variables.product.prodname_discussions %} | | | | **✔️** | **✔️** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions) to a new repository| | | **✔️** | **✔️** | **✔️** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **✔️** | | **✔️** | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| Create [codespaces](/codespaces/about-codespaces) | | | **✔️** | **✔️** | **✔️** |{% endif %} ### Access requirements for security features @@ -153,18 +153,18 @@ In this section, you can find the access required for security features, such as | Repository action | Read | Triage | Write | Maintain | Admin | |:---|:---:|:---:|:---:|:---:|:---:| -| Receive [{% data variables.product.prodname_dependabot_alerts %} for insecure dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | -| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% ifversion ghes or ghae or ghec %} -| [Designate additional people or teams to receive security alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} -| Create [security advisories](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} -| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} -| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} -| [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | -| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | -| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} -| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} -| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **X** |{% endif %} +| Receive [{% data variables.product.prodname_dependabot_alerts %} for insecure dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **✔️** | +| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **✔️** |{% ifversion ghes or ghae or ghec %} +| [Designate additional people or teams to receive security alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| Create [security advisories](/code-security/security-advisories/about-github-security-advisories) | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %} +| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **✔️** | **✔️** | **✔️** | +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% ifversion ghes or ghae or ghec %} +| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **✔️** |{% endif %} [1] Repository writers and maintainers can only see alert information for their own commits. diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index 91ce1f4dc4..4da00a0450 100644 --- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -12,21 +12,19 @@ topics: shortTitle: IAM con el SSO de SAML --- -{% data reusables.enterprise-accounts.emu-saml-note %} +{% data reusables.saml.ghec-only %} ## Acerca de SAML SSO {% data reusables.saml.dotcom-saml-explanation %} -{% data reusables.saml.ghec-only %} - {% data reusables.saml.saml-accounts %} Los propietarios de las organizaciones pueden requerir el SSO de SAML para una organización individual o para todas las organizaciones en una cuenta empresarial. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML para tu empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)". {% data reusables.saml.outside-collaborators-exemption %} -Antes de habilitar el SSO de SAML para tu organización, necesitarás conectar tu IdP a la misma. Para obtener más información, consulta "[Conectar tu proveedor de identidad a tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)." +Antes de habilitar el SSO de SAML para tu organización, necesitarás conectar tu IdP a la misma. Para obtener más información, consulta la sección "[Conectar a tu proveedor de identidad con tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)." En una organización, el SSO de SAML puede inhabilitarse, habilitarse pero no requerirse, o habilitarse y requerirse. Después de habilitar exitosamente el SSO de SAML para tu organización y que sus miembros se autentiquen exitosamente con tu IdP, puedes requerir la configuración del SSO de SAML. Para obtener más información acerca de requerir el SSO de SAML para tu organización en {% data variables.product.prodname_dotcom %}, consulta la sección "[Requerir el inicio de sesión único de SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)". diff --git a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md index 6c0cb23014..5b5dac7385 100644 --- a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md +++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md @@ -18,6 +18,8 @@ Verifying your domain stops other GitHub users from taking over your custom doma When you verify a domain, any immediate subdomains are also included in the verification. For example, if the `github.com` custom domain is verified, `docs.github.com`, `support.github.com`, and any other immediate subdomains will also be protected from takeovers. +{% data reusables.pages.wildcard-dns-warning %} + It's also possible to verify a domain for your organization{% ifversion ghec %} or enterprise{% endif %}, which displays a "Verified" badge on the organization {% ifversion ghec %}or enterprise{% endif %} profile{% ifversion ghec %} and, on {% data variables.product.prodname_ghe_cloud %}, allows you to restrict notifications to email addresses using the verified domain{% endif %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization){% ifversion ghec %}" and "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% endif %}." ## Verifying a domain for your user site @@ -28,7 +30,7 @@ It's also possible to verify a domain for your organization{% ifversion ghec %} 1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `USERNAME` with your username and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output. ``` dig _github-pages-challenge-USERNAME.example.com +nostats +nocomments +nocmd TXT - ``` + ``` {% data reusables.pages.settings-verify-domain-confirm %} ## Verifying a domain for your organization site @@ -42,5 +44,5 @@ Organization owners can verify custom domains for their organization. 1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `ORGANIZATION` with the name of your organization and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output. ``` dig _github-pages-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT - ``` + ``` {% data reusables.pages.settings-verify-domain-confirm %} diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/es-ES/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md index 66ecf31a2b..2bc9b70a38 100644 --- a/translations/es-ES/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md @@ -22,7 +22,7 @@ permissions: 'People with admin permissions for a repository can use the theme c {% note %} -**Note**: The Jekyll theme chooser is not supported for {% data variables.product.prodname_pages %} sites that are published with a custom {% data variables.product.prodname_actions %} workflow. If you build your site with Jekyll and publish your site with a custom {% data variables.product.prodname_actions %} workflow, you can add a theme by editing the `_config.yml` file. For more information, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)." +**Nota**: El selector de tema de Jekyll no es compatible para los sitios de {% data variables.product.prodname_pages %} que se publican con un flujo de trabajo de {% data variables.product.prodname_actions %} personalizado. Si compilas tu sitio con Jekyll y lo publicas con un flujo de trabajo de {% data variables.product.prodname_actions %} personalizado, puedes agregar un tema editando el archivo `_config.yml`. Para obtener más información, consulta "[Agregar un tema a tu sitio de GitHub Pages con Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)". {% endnote %} diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/es-ES/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md index 976dfd552d..53cb3c04b6 100644 --- a/translations/es-ES/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -46,17 +46,11 @@ shortTitle: Configurar la fuenta de publicción Si eliges la carpeta de `docs` en cualquier rama como tu fuente de publicación y luego eliminas la carpeta de `/docs` de esta rama en tu repositorio posteriormente, tu sitio no se creará y obtendrás un mensaje de error de creación de página debido a una carpeta `/docs` faltante. Para obtener más información, consulta "[Solución de problemas de errores de compilación de Jekyll para los sitios de {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)". -{% ifversion fpt %} +{% ifversion build-pages-with-actions %} Tu sitio de {% data variables.product.prodname_pages %} siempre se desplegará con una ejecución de flujo de trabajo de {% data variables.product.prodname_actions %}, incluso si configuraste tu sitio de {% data variables.product.prodname_pages %} para que compilara utilizando una herramienta de IC distinta. La mayoría de los flujos de trabajo de IC externos se "despliegan" en las GitHub Pages cuando confirmas la salida de compilación en la rama de `gh-pages` del repositorio y, habitualmente, incluyen un archivo de `.nojekyll`. Cuando esto sucede, el flujo de trabajo de {% data variables.product.prodname_actions %} detectará el estado en el que la rama no necesita un paso de compilación y ejecutará solo los pasos necesarios para desplegar el sitio a los servidores de {% data variables.product.prodname_pages %}. -Para encontrar errores potenciales en ya sea la compilación o el despliegue, puedes verificar la ejecución de flujo de trabajo para tu sitio de {% data variables.product.prodname_pages %} si revisas las ejecuciones de flujo de trabajo del repositorio. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". Para obtener más información sobre cómo volver a ejecutar el flujo de trabajo en caso de encontrar une error, consulta la sección "[Volver a ejecutar flujos de trabajo y jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)". - -{% note %} - -{% data reusables.pages.pages-builds-with-github-actions-public-beta %} - -{% endnote %} +Para encontrar errores potenciales en ya sea la compilación o el despliegue, puedes verificar la ejecución de flujo de trabajo para tu sitio de {% data variables.product.prodname_pages %} si revisas las ejecuciones de flujo de trabajo del repositorio. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". Para obtener más información sobre cómo volver a ejecutar el flujo de trabajo en caso de encontrar une error, consulta la sección "[Volver a ejecutar flujos de trabajo y jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)". {% endif %} diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md index 075304be17..ac69466cb7 100644 --- a/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md @@ -41,11 +41,11 @@ shortTitle: Crear un sitio de GitHub Pages {% data reusables.pages.navigate-site-repo %} {% data reusables.pages.decide-publishing-source %} -1. Create the entry file for your site. {% data variables.product.prodname_pages %} will look for an `index.html`, `index.md`, or `README.md` file as the entry file for your site. +1. Crea el archivo de entrada para tu sitio. {% data variables.product.prodname_pages %} buscará un archivo `index.html`, `index.md` o `README.md` como el archivo de entrada para tu sitio. - {% ifversion pages-custom-workflow %}If your publishing source is a branch and folder, the entry file must be at the top level of the source folder on the source branch. For example, if your publishing source is the `/docs` folder on the `main` branch, your entry file must be located in the `/docs` folder on a branch called `main`. + {% ifversion pages-custom-workflow %}Si tu fuente de publicación es una rama y carpeta, el archivo de entrada debe estar en el nivel superior de la carpeta origen en la rama origen. Por ejemplo, si tu fuente de publicación es la carpeta `/docs` en la rama `main`, tu archivo de entrada debe estar ubicado en la carpeta `/docs` en una rama llamada `main`. - If your publishing source is a {% data variables.product.prodname_actions %} workflow, the artifact that you deploy must include the entry file at the top level of the artifact. Instead of adding the entry file to your repository, you may choose to have your {% data variables.product.prodname_actions %} workflow generate your entry file when the workflow runs.{% else %} The entry file must be at the top level of your chosen publishing source. For example, if your publishing source is the `/docs` folder on the `main` branch, your entry file must be located in the `/docs` folder on a branch called `main`.{% endif %} + Si tu fuente de publicación es un flujo de trabajo de {% data variables.product.prodname_actions %}, el artefacto que despliegues deberá incluir el archivo de entrada en el nivel superior del mismo. En vez de agregar el archivo de entrada a tu repositorio, puedes elegir que tu flujo de trabajo de {% data variables.product.prodname_actions %} genere tu archivo de entrada cuando se ejecute.{% else %} El archivo de entrada debe estar en el nivel superior de la fuente de publicación que elijas. Por ejemplo, si tu fuente de publicación es la carpeta `/docs` en la rama `main`, tu archivo de entrada debe estar ubicado en la carpeta `/docs` en una rama llamada `main`.{% endif %} {% data reusables.pages.configure-publishing-source %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %} diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md index b76538436f..9e84172aa2 100644 --- a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -30,26 +30,27 @@ shortTitle: Jekyll build errors for Pages {% endnote %} +{% ifversion build-pages-with-actions %} +If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. +{% else %} If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. There are two main types of Jekyll build error messages. - A "Page build warning" message means your build completed successfully, but you may need to make changes to prevent future problems. - A "Page build failed" message means your build failed to complete. If Jekyll is able to detect a reason for the failure, you'll see a descriptive error message. +{% endif %} For more information about troubleshooting build errors, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)." -{% ifversion fpt %} +{% ifversion build-pages-with-actions %} ## Viewing Jekyll build error messages with {% data variables.product.prodname_actions %} By default, your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. To find potential build errors, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." -{% note %} - -{% data reusables.pages.pages-builds-with-github-actions-public-beta %} - -{% endnote %} {% endif %} +{% ifversion build-pages-with-actions %}{% else %} ## Viewing your repository's build failures on {% data variables.product.product_name %} You can see build failures (but not build warnings) for your site on {% data variables.product.product_name %} in the **Settings** tab of your site's repository. +{% endif %} ## Viewing Jekyll build error messages locally @@ -63,7 +64,7 @@ We recommend testing your site locally, which allows you to see build error mess ## Viewing Jekyll build errors by email -{% ifversion pages-custom-workflow %}If you are publishing from a branch, when{% else %}When{% endif %} you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. You'll also receive emails for build warnings. {% data reusables.pages.build-failure-email-server %} +{% ifversion pages-custom-workflow %}If you are publishing from a branch, when{% else %}When{% endif %} you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. {% data reusables.pages.build-failure-email-server %} {% ifversion pages-custom-workflow %}If you are publishing with a custom {% data variables.product.prodname_actions %} workflow, in order to receive emails about build errors in your pull request, you must configure your workflow to run on the `pull_request` trigger. When you do this, we recommend that you skip any deploy steps if the workflow was triggered by the `pull_request` event. This will allow you to see any build errors without deploying the changes from your pull request to your site. For more information, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows#pull_request)" and "[Expressions](/actions/learn-github-actions/expressions)."{% endif %} diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md index f2bc4e9bfd..521d8fef16 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -25,6 +25,7 @@ You can create a branch in different ways on {% data variables.product.product_n {% endnote %} +{% ifversion create-branch-from-overview %} ### Creating a branch via the branches overview {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-branches %} @@ -35,6 +36,7 @@ You can create a branch in different ways on {% data variables.product.product_n ![Screenshot of branch creation modal for a fork with branch source emphasized](/assets/images/help/branches/branch-creation-popup-branch-source.png) 3. Click **Create branch**. ![Screenshot of branch creation modal with create branch button emphasized](/assets/images/help/branches/branch-creation-popup-button.png) +{% endif %} ### Creating a branch using the branch dropdown {% data reusables.repositories.navigate-to-repo %} @@ -44,10 +46,12 @@ You can create a branch in different ways on {% data variables.product.product_n ![branch selector menu](/assets/images/help/branch/branch-selection-dropdown.png) 1. Type a unique name for your new branch, then select **Create branch**. ![branch creation text box](/assets/images/help/branch/branch-creation-text-box.png) + {% ifversion fpt or ghec or ghes > 3.4 %} ### Creating a branch for an issue You can create a branch to work on an issue directly from the issue page and get started right away. For more information, see "[Creating a branch to work on an issue](/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue)". {% endif %} + ## Deleting a branch {% data reusables.pull_requests.automatically-delete-branches %} diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md index 2f9edbd00a..b1b70872ec 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md @@ -23,11 +23,18 @@ permissions: People with write access for a forked repository can sync the fork ## Syncing a fork branch from the web UI +{% ifversion syncing-fork-web-ui %} 1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. -2. Select the **Fetch upstream** drop-down. +2. Select the **Sync fork** dropdown. + !["Sync fork" dropdown emphasized](/assets/images/help/repository/sync-fork-dropdown.png) +3. Review the details about the commits from the upstream repository, then click **Update branch**. + ![Sync fork modal with "Update branch" button emphasized](/assets/images/help/repository/update-branch-button.png) +{% else %} +1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. +2. Select the **Fetch upstream** dropdown. !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png) 3. Review the details about the commits from the upstream repository, then click **Fetch and merge**. - !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png) + !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts. diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md index 739df8c64c..4f3d51796c 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md @@ -1,6 +1,6 @@ --- -title: 'Disabling {% data variables.projects.projects_v1_boards %} in a repository' -intro: 'Repository administrators can turn off {% data variables.projects.projects_v1_boards %} for a repository if you or your team manages work differently.' +title: 'Inhabilitar los {% data variables.projects.projects_v1_boards %} en un repositorio' +intro: 'Los administradores de repositorio pueden apagar los {% data variables.projects.projects_v1_boards %} para un repositorio si tú o tu equipo administra el trabajo de forma distinta.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-a-repository - /articles/disabling-project-boards-in-a-repository @@ -13,11 +13,11 @@ versions: ghec: '*' topics: - Pull requests -shortTitle: 'Disable {% data variables.projects.projects_v1_boards %}' +shortTitle: 'Inhabilitar los {% data variables.projects.projects_v1_boards %}' allowTitleToDifferFromFilename: true --- -When you disable {% data variables.projects.projects_v1_boards %}, you will no longer see {% data variables.projects.projects_v1_board %} information in timelines or [audit logs](/articles/reviewing-your-security-log/). +Cuando inhabilitas los {% data variables.projects.projects_v1_boards %}, ya no verás la información del {% data variables.projects.projects_v1_board %} en las líneas de tiempo ni en las [bitácoras de auditoría](/articles/reviewing-your-security-log/). {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-for-repositories.md b/translations/es-ES/content/search-github/searching-on-github/searching-for-repositories.md index 1f28521363..ebdc2c2d2a 100644 --- a/translations/es-ES/content/search-github/searching-on-github/searching-for-repositories.md +++ b/translations/es-ES/content/search-github/searching-on-github/searching-for-repositories.md @@ -91,7 +91,7 @@ Puedes buscar repositorios con base en la cantidad de estrellas que tienen, util | Qualifier | Ejemplo | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) encuentra repositorios con exactamente 500 estrellas. | -| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) encuentra repositorios con 10 a 20 estrellas, que son menores que 1000 KB. | +| | [**stars:10..20 size:<1000**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB. | | | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) encuentra repositorios con al menos 500 estrellas, incluidas los bifurcados, que están escritos en PHP. | ## Buscar por cuándo fue creado o actualizado por última vez un repositorio diff --git a/translations/es-ES/data/features/build-pages-with-actions.yml b/translations/es-ES/data/features/build-pages-with-actions.yml new file mode 100644 index 0000000000..0e80ab5a21 --- /dev/null +++ b/translations/es-ES/data/features/build-pages-with-actions.yml @@ -0,0 +1,5 @@ +#Issue 7584 +#Building Pages sites with Actions [GA] +versions: + fpt: '*' + ghec: '*' diff --git a/translations/es-ES/data/features/create-branch-from-overview.yml b/translations/es-ES/data/features/create-branch-from-overview.yml new file mode 100644 index 0000000000..a51e624c41 --- /dev/null +++ b/translations/es-ES/data/features/create-branch-from-overview.yml @@ -0,0 +1,5 @@ +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.7' + ghae: 'issue-6670' diff --git a/translations/es-ES/data/features/security-overview-displayed-alerts.yml b/translations/es-ES/data/features/security-overview-displayed-alerts.yml new file mode 100644 index 0000000000..da84d07e41 --- /dev/null +++ b/translations/es-ES/data/features/security-overview-displayed-alerts.yml @@ -0,0 +1,6 @@ +#Reference: #7114. +#Documentation for security overview availability to all enterprise accounts. +versions: + ghec: '*' + ghes: '>=3.7' + ghae: 'issue-7114' diff --git a/translations/es-ES/data/features/syncing-fork-web-ui.yml b/translations/es-ES/data/features/syncing-fork-web-ui.yml new file mode 100644 index 0000000000..72bf3f5878 --- /dev/null +++ b/translations/es-ES/data/features/syncing-fork-web-ui.yml @@ -0,0 +1,7 @@ +#Issue 7629 +#Improved UI for manually syncing a fork +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.7' + ghae: 'issue-7629' diff --git a/translations/es-ES/data/features/totp-and-mobile-sudo-challenge.yml b/translations/es-ES/data/features/totp-and-mobile-sudo-challenge.yml index 0eae9cda9c..f32fb6b9ee 100644 --- a/translations/es-ES/data/features/totp-and-mobile-sudo-challenge.yml +++ b/translations/es-ES/data/features/totp-and-mobile-sudo-challenge.yml @@ -1,5 +1,5 @@ #TOTP and mobile challenge for sudo mode prompt. versions: - fpt: '*' - ghec: '*' + #fpt: '*' + #ghec: '*' ghes: '>= 3.7' diff --git a/translations/es-ES/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml b/translations/es-ES/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml index f973b323b7..9e7d70e460 100644 --- a/translations/es-ES/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml +++ b/translations/es-ES/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml @@ -156,7 +156,7 @@ upcoming_changes: owner: lukewar - location: ProjectNextFieldType.TASKS - description: '`TASKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: 'Se eliminará a `TASKS`. Sigue la guía de ProjectV2 en https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ para encontrar un reemplazo adecuado.' reason: La API de `ProjectNext` quedará obsoleta para favorecer la API de `ProjectV2`, la cual tiene mayores capacidades. date: '2022-10-01T00:00:00+00:00' criticality: breaking diff --git a/translations/es-ES/data/graphql/ghec/graphql_upcoming_changes.public.yml b/translations/es-ES/data/graphql/ghec/graphql_upcoming_changes.public.yml index 2bd16d5764..d0e5b6ac20 100644 --- a/translations/es-ES/data/graphql/ghec/graphql_upcoming_changes.public.yml +++ b/translations/es-ES/data/graphql/ghec/graphql_upcoming_changes.public.yml @@ -576,7 +576,7 @@ upcoming_changes: owner: lukewar - location: ProjectNextFieldType.TASKS - description: '`TASKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: 'Se eliminará a `TASKS`. Sigue la guía de ProjectV2 en https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ para encontrar un reemplazo adecuado.' reason: La API de `ProjectNext` quedará obsoleta para favorecer la API de `ProjectV2`, la cual tiene mayores capacidades. date: '2022-10-01T00:00:00+00:00' criticality: breaking diff --git a/translations/es-ES/data/graphql/graphql_upcoming_changes.public.yml b/translations/es-ES/data/graphql/graphql_upcoming_changes.public.yml index 2bd16d5764..d0e5b6ac20 100644 --- a/translations/es-ES/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/es-ES/data/graphql/graphql_upcoming_changes.public.yml @@ -576,7 +576,7 @@ upcoming_changes: owner: lukewar - location: ProjectNextFieldType.TASKS - description: '`TASKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: 'Se eliminará a `TASKS`. Sigue la guía de ProjectV2 en https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ para encontrar un reemplazo adecuado.' reason: La API de `ProjectNext` quedará obsoleta para favorecer la API de `ProjectV2`, la cual tiene mayores capacidades. date: '2022-10-01T00:00:00+00:00' criticality: breaking diff --git a/translations/es-ES/data/reusables/actions/jobs/multi-dimension-matrix.md b/translations/es-ES/data/reusables/actions/jobs/multi-dimension-matrix.md index f5bf24c91c..ae1d08acfd 100644 --- a/translations/es-ES/data/reusables/actions/jobs/multi-dimension-matrix.md +++ b/translations/es-ES/data/reusables/actions/jobs/multi-dimension-matrix.md @@ -12,7 +12,7 @@ jobs: example_matrix: strategy: matrix: - os: [ubuntu-18.04, ubuntu-20.04] + os: [ubuntu-22.04, ubuntu-20.04] version: [10, 12, 14] runs-on: {% raw %}${{ matrix.os }}{% endraw %} steps: diff --git a/translations/es-ES/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md b/translations/es-ES/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md index c4c3102691..a07502ccf2 100644 --- a/translations/es-ES/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md +++ b/translations/es-ES/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md @@ -6,7 +6,7 @@ Utiliza `jobs..runs-on` para definir el tipo de máquina en la cuál eje ### Elegir los ejecutores hospedados en {% data variables.product.prodname_dotcom %} -Si usas un ejecutor alojado {% data variables.product.prodname_dotcom %}, cada trabajo se ejecuta en una nueva instancia de un entorno virtual especificado por `runs-on`. +If you use a {% data variables.product.prodname_dotcom %}-hosted runner, each job runs in a fresh instance of a runner image specified by `runs-on`. Los tipos de ejecutores alojados {% data variables.product.prodname_dotcom %} disponibles son: @@ -18,7 +18,7 @@ Los tipos de ejecutores alojados {% data variables.product.prodname_dotcom %} di runs-on: ubuntu-latest ``` -Para obtener más información, consulta "[Entornos virtuales para ejecutores alojados de {% data variables.product.prodname_dotcom %}](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)". +Para obtener más información, consulta la sección "[Acerca de los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/using-github-hosted-runners/about-github-hosted-runners)". {% endif %} {% ifversion fpt or ghec or ghes %} diff --git a/translations/es-ES/data/reusables/actions/macos-runner-preview.md b/translations/es-ES/data/reusables/actions/macos-runner-preview.md index 8ca052061f..c9b93aecbe 100644 --- a/translations/es-ES/data/reusables/actions/macos-runner-preview.md +++ b/translations/es-ES/data/reusables/actions/macos-runner-preview.md @@ -1 +1 @@ -La etiqueta de flujo de trabajo de YAML macos-latest utiliza actualmente el ambiente virtual de macOS 10.15. +The macos-latest YAML workflow label currently uses the macOS 10.15 runner image. diff --git a/translations/es-ES/data/reusables/actions/pure-javascript.md b/translations/es-ES/data/reusables/actions/pure-javascript.md index a69d63d0bd..cf574fb47a 100644 --- a/translations/es-ES/data/reusables/actions/pure-javascript.md +++ b/translations/es-ES/data/reusables/actions/pure-javascript.md @@ -1 +1 @@ -Para garantizar que tus acciones de JavaScript son compatibles con todos los ejecutores hospedados en GitHub (Ubuntu, Windows, y macOS), el código empaquetado de JavaScript que escribas debe ser puramente JavaScript y no depender de otros binarios. Las acciones de JavaScript se ejecutan directamente en el ejecutor y utiliza binarios que ya existen en el ambiente virtual. +Para garantizar que tus acciones de JavaScript son compatibles con todos los ejecutores hospedados en GitHub (Ubuntu, Windows, y macOS), el código empaquetado de JavaScript que escribas debe ser puramente JavaScript y no depender de otros binarios. JavaScript actions run directly on the runner and use binaries that already exist in the runner image. diff --git a/translations/es-ES/data/reusables/actions/supported-github-runners.md b/translations/es-ES/data/reusables/actions/supported-github-runners.md index edd94968e7..64c4a3ace3 100644 --- a/translations/es-ES/data/reusables/actions/supported-github-runners.md +++ b/translations/es-ES/data/reusables/actions/supported-github-runners.md @@ -1,7 +1,7 @@ - + @@ -36,7 +36,6 @@ Ubuntu 22.04 ubuntu-22.04 @@ -49,12 +48,13 @@ Ubuntu 20.04 @@ -92,7 +92,7 @@ Migra a macOS-11 o macOS-12. Para obtener más informa {% note %} -**Nota:** Los ambientes virtuales `más recientes` son las últimas imágenes estables que proporciona {% data variables.product.prodname_dotcom %} y puede que no sean las versiones más recientes de los sistemas operativos disponibles desde los proveedores de estos. +**Note:** The `-latest` runner images are the latest stable images that {% data variables.product.prodname_dotcom %} provides, and might not be the most recent version of the operating system available from the operating system vendor. {% endnote %} diff --git a/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md index d84e1d5bc5..d594cdac5f 100644 --- a/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md +++ b/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md @@ -19,7 +19,11 @@ Después de que conectes tu cuenta de {% data variables.product.product_location ![Buscar una rama para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-branch-vscode.png) -5. Haz clic en el tipo de máquina que quieras utilizar. +5. If prompted to choose a dev container configuration file, choose a file from the list. + + ![Choosing a dev container configuration file for {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-dev-container-vscode.png) + +6. Haz clic en el tipo de máquina que quieras utilizar. ![Tipos de instancia para un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-sku-vscode.png) diff --git a/translations/es-ES/data/reusables/gated-features/advanced-security.md b/translations/es-ES/data/reusables/gated-features/advanced-security.md deleted file mode 100644 index 5c4bd3d348..0000000000 --- a/translations/es-ES/data/reusables/gated-features/advanced-security.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_GH_advanced_security %} is a set of security features designed to make enterprise code more secure. Está disponible para {% data variables.product.prodname_ghe_server %} 3.0 o superior, {% data variables.product.prodname_ghe_cloud %} y para los repositorios de código abierto. Para aprender más sobre las características que se incluyen en la {% data variables.product.prodname_GH_advanced_security %}, consulta la sección "[Acerca del {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)". diff --git a/translations/es-ES/data/reusables/gated-features/environments.md b/translations/es-ES/data/reusables/gated-features/environments.md index 09f7a978ab..3c46e9f446 100644 --- a/translations/es-ES/data/reusables/gated-features/environments.md +++ b/translations/es-ES/data/reusables/gated-features/environments.md @@ -1 +1 @@ -Los ambientes, las reglas de protección de ambiente y los secretos de ambiente se encuentran disponibles en los repositorios **públicos** para todos los productos. Para tener acceso a los ambientes en los repositorios **privados**, debes utilizar {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info %} +Los ambientes, las reglas de protección de ambiente y los secretos de ambiente se encuentran disponibles en los repositorios **públicos** para todos los productos. For access to environments in **private** or **internal** repositories, you must use {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info %} diff --git a/translations/es-ES/data/reusables/gated-features/ghas.md b/translations/es-ES/data/reusables/gated-features/ghas.md index 060b70911a..d8380c191c 100644 --- a/translations/es-ES/data/reusables/gated-features/ghas.md +++ b/translations/es-ES/data/reusables/gated-features/ghas.md @@ -1 +1 @@ -La {% data variables.product.prodname_GH_advanced_security %} se encuentra disponible para las cuentas empresariales en {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} y {% data variables.product.prodname_ghe_server %} 3.0 o superior.{% ifversion fpt or ghec %} La {% data variables.product.prodname_GH_advanced_security %} también se incluye en todos los repositorios públicos en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Acerca de los productos de GitHub](/github/getting-started-with-github/githubs-products)".{% else %} Para obtener más información sobre cómo mejorar tu instancia de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)" y refiérete al [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) para encontrar la ruta de mejora desde tu versión de lanzamiento actual.{% endif %} +{% data variables.product.prodname_GH_advanced_security %} está disponible para las cuentas empresariales en {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} y {% data variables.product.prodname_ghe_server %}.{% ifversion fpt or ghec %} Algunas características de {% data variables.product.prodname_GH_advanced_security %} también están disponibles para los repositorios públicos en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Acerca de los productos de GitHub](/github/getting-started-with-github/githubs-products)".{% else %} Para obtener más información sobre cómo mejorar tu instancia de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)" y refiérete al [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) para encontrar la ruta de mejora desde tu versión de lanzamiento actual.{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/security-overview.md b/translations/es-ES/data/reusables/gated-features/security-overview.md index 6d18589b0a..da2ff05c9f 100644 --- a/translations/es-ES/data/reusables/gated-features/security-overview.md +++ b/translations/es-ES/data/reusables/gated-features/security-overview.md @@ -1,6 +1,9 @@ -{% ifversion ghae %} -El resumen de seguridad de tu organización se encuentra disponible si tienes una licencia para la {% data variables.product.prodname_GH_advanced_security %}, la cual es gratuita durante el lanzamiento beta. {% data reusables.advanced-security.more-info-ghas %} -{% elsif ghec or ghes %} +{% ifversion fpt %} +The security overview is available for organizations that use {% data variables.product.prodname_enterprise %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". +{% elsif security-overview-displayed-alerts %} +All organizations and enterprises have a security overview. If you use {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghae %}, which is free during the beta release,{% endif %} you will see additional information. {% data reusables.advanced-security.more-info-ghas %} +{% elsif ghes < 3.7 %} El resumen de seguridad de tu organización se encuentra disponible si tienes una licencia para la {% data variables.product.prodname_GH_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %} -{% elsif fpt %} -El resumen de seguridad se encuentra disponible para las organizaciones que utilizan {% data variables.product.prodname_enterprise %} y tienen una licencia para {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información, consulta la sección "[Acerca de la {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)". {% endif %} +{% elsif ghae %} +A security overview for your enterprise and for organizations is available if you use {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release. {% data reusables.advanced-security.more-info-ghas %} +{% endif %} diff --git a/translations/es-ES/data/reusables/getting-started/math-and-diagrams.md b/translations/es-ES/data/reusables/getting-started/math-and-diagrams.md new file mode 100644 index 0000000000..0b8fd102b4 --- /dev/null +++ b/translations/es-ES/data/reusables/getting-started/math-and-diagrams.md @@ -0,0 +1 @@ +{% ifversion mermaid %}You can use Markdown to add rendered math expressions, diagrams, maps, and 3D models to your wiki. For more information on creating rendered math expressions, see "[Writing mathematical expressions](/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions)." For more information on creating diagrams, maps and 3D models, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)."{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/pages/check-workflow-run.md b/translations/es-ES/data/reusables/pages/check-workflow-run.md index 129d8ebf7d..242afa6718 100644 --- a/translations/es-ES/data/reusables/pages/check-workflow-run.md +++ b/translations/es-ES/data/reusables/pages/check-workflow-run.md @@ -1,8 +1,10 @@ -{% ifversion fpt %} -1. Unless your {% data variables.product.prodname_pages %} site is built from a private or internal repository and published from a branch, your site is built and deployed with a {% data variables.product.prodname_actions %} workflow. Para obtener más información sobre cómo ver el estado del flujo de trabajo, consulta la sección "[Ver el historial de ejecución del flujo de trabajo](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". +{% ifversion build-pages-with-actions %} +1. Your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". -{% note %} + {% note %} -{% data reusables.pages.pages-builds-with-github-actions-public-beta %} + **Note:** {% data variables.product.prodname_actions %} is free for public repositories. Usage charges apply for private and internal repositories that go beyond the monthly allotment of free minutes. Para obtener más información, consulta la sección "[Límites de uso, facturación y administración](/actions/reference/usage-limits-billing-and-administration)". -{% endnote %}{% endif %} + {% endnote %} + +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/pages/decide-publishing-source.md b/translations/es-ES/data/reusables/pages/decide-publishing-source.md index 28907ae368..228d31ddd0 100644 --- a/translations/es-ES/data/reusables/pages/decide-publishing-source.md +++ b/translations/es-ES/data/reusables/pages/decide-publishing-source.md @@ -1 +1 @@ -1. Decide qué fuente de publicación quieres utilizar. For more information, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." +1. Decide qué fuente de publicación quieres utilizar. Para obtener más información, consulta la sección "[Configurar una fuente de publicación para tu sitio de GitHub Pages](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)". diff --git a/translations/es-ES/data/reusables/pages/navigate-publishing-source.md b/translations/es-ES/data/reusables/pages/navigate-publishing-source.md index a0efb6048e..ed4863edf6 100644 --- a/translations/es-ES/data/reusables/pages/navigate-publishing-source.md +++ b/translations/es-ES/data/reusables/pages/navigate-publishing-source.md @@ -1 +1 @@ -1. Navega a la fuente de publicación para tu sitio. For more information, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." +1. Navega a la fuente de publicación para tu sitio. Para obtener más información, consulta la sección "[Configurar una fuente de publicación para tu sitio de GitHub Pages](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)". diff --git a/translations/es-ES/data/reusables/pages/pages-builds-with-github-actions-public-beta.md b/translations/es-ES/data/reusables/pages/pages-builds-with-github-actions-public-beta.md deleted file mode 100644 index 7ba0a0ca1e..0000000000 --- a/translations/es-ES/data/reusables/pages/pages-builds-with-github-actions-public-beta.md +++ /dev/null @@ -1,5 +0,0 @@ -{% ifversion fpt %} - -**Nota:** El flujo de {% data variables.product.prodname_actions %} que se ejecuta para tus sitios de {% data variables.product.prodname_pages %} se encuentra en beta público para los repositorios públicos y está sujeto a cambios. Los flujos de trabajo de {% data variables.product.prodname_actions %} son gratuitos para los repositorios públicos. - -{% endif %} diff --git a/translations/es-ES/data/reusables/pages/wildcard-dns-warning.md b/translations/es-ES/data/reusables/pages/wildcard-dns-warning.md index e7f527e8c7..5a407546e3 100644 --- a/translations/es-ES/data/reusables/pages/wildcard-dns-warning.md +++ b/translations/es-ES/data/reusables/pages/wildcard-dns-warning.md @@ -1,5 +1,5 @@ {% warning %} -**Advertencia:** Es altamente recomendable no utilizar registros DNS comodines, como `*.example.com`. Un registro DNS comodín le permitirá a cualquiera que aloje un sitio {% data variables.product.prodname_pages %} en uno de tus subdominios. +**Advertencia:** Es altamente recomendable no utilizar registros DNS comodines, como `*.example.com`. A wildcard DNS record will allow anyone to host a {% data variables.product.prodname_pages %} site at one of your subdomains even when they are verified. Para obtener más información, consulta la sección "[Verificar tu dominio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)". {% endwarning %} diff --git a/translations/es-ES/data/reusables/projects/create-project.md b/translations/es-ES/data/reusables/projects/create-project.md index 096da728b9..bb6d227d92 100644 --- a/translations/es-ES/data/reusables/projects/create-project.md +++ b/translations/es-ES/data/reusables/projects/create-project.md @@ -1,7 +1,7 @@ {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} 1. Debajo de tu nombre de organización, da clic en {% octicon "table" aria-label="The project icon" %}**Proyectos**. ![Screenshot showing the 'Projects' tab](/assets/images/help/projects-v2/tab-projects.png) -1. Click **New project**. ![Screenshot showing New project button](/assets/images/help/projects-v2/new-project-button.png) +1. Click **New project**. ![Captura de pantalla que muestra el botón de proyecto nuevo](/assets/images/help/projects-v2/new-project-button.png) 1. When prompted to select a template, click a template or, to start with an empty project, click **Table** or **Board**. Luego, haz clic en **Crear**. ![Captura de pantalla que muestra el modo de selección de plantilla](/assets/images/help/issues/projects-select-template.png) diff --git a/translations/es-ES/data/reusables/projects/project_boards_old.md b/translations/es-ES/data/reusables/projects/project_boards_old.md index 2b505bb2e0..0d0843a9d9 100644 --- a/translations/es-ES/data/reusables/projects/project_boards_old.md +++ b/translations/es-ES/data/reusables/projects/project_boards_old.md @@ -3,8 +3,8 @@ {% note %} **Notas:** -* {% data variables.product.prodname_projects_v2 %}, the all-new projects experience, is now available. For more information about {% data variables.product.prodname_projects_v2 %}, see "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)" and for information about migrating your {% data variables.projects.projects_v1_board %}, see "[Migrating from {% data variables.product.prodname_projects_v1_caps %}](/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic)." -* Solo puedes crear un tablero de proyecto clásico y nuevo para una organización, usuario o repositorio que ya tenga por lo menos un tablero de proyecto clásico. If you're unable to create a classic project board, create a project board instead. +* {% data variables.product.prodname_projects_v2 %}, la experiencia completamente nueva de los proyectos ya está disponible. Para obtener más información sobre {% data variables.product.prodname_projects_v2 %}, consulta la sección "[Acerca de los {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)" y para obtener información de cómo migrar tu {% data variables.projects.projects_v1_board %}, consulta la sección "[Migrarte desde los {% data variables.product.prodname_projects_v1_caps %}](/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic)". +* Solo puedes crear un tablero de proyecto clásico y nuevo para una organización, usuario o repositorio que ya tenga por lo menos un tablero de proyecto clásico. Si no puedes crear un tablero de proyecto clásico, crea un tablero de proyecto en su lugar. {% endnote %} diff --git a/translations/es-ES/data/reusables/saml/dotcom-saml-explanation.md b/translations/es-ES/data/reusables/saml/dotcom-saml-explanation.md index ffd406e5f6..c70655f0d7 100644 --- a/translations/es-ES/data/reusables/saml/dotcom-saml-explanation.md +++ b/translations/es-ES/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -El inicio de sesión único (SSO) de SAML proporciona a los propietarios de las organizaciones y empresas que utilizan {% data variables.product.product_name %} una forma de controlar y asegurar el acceso a los recursos organizacionales como los repositorios, propuestas y solicitudes de cambios. +El inicio de sesión único (SSO) de SAML proporciona a los propietarios de las organizaciones y empresas que utilizan {% data variables.product.product_name %} una forma de controlar y asegurar el acceso a los recursos organizacionales como los repositorios, propuestas y solicitudes de cambios. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/saml/outside-collaborators-exemption.md b/translations/es-ES/data/reusables/saml/outside-collaborators-exemption.md index d95afb05b1..023d196237 100644 --- a/translations/es-ES/data/reusables/saml/outside-collaborators-exemption.md +++ b/translations/es-ES/data/reusables/saml/outside-collaborators-exemption.md @@ -1,5 +1,8 @@ {% note %} -**Nota:** No se requiere que los colaboradores externos se autentiquen con un IdP para acceder a los recursos de una organización que cuente con el SSO de SAML. Para obtener más información sobre los colaboradores externos, consulta la sección "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)". +**Notas:** + +- No se requiere autenticación de SAML para que los miembros de las organizaciones realicen operaciones de lectura tales como ver, clonar y bifurcar recursos públicos. +- No se requiere autenticación de SAML para los colaboradores externos. Para obtener más información sobre los colaboradores externos, consulta la sección "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)". {% endnote %} diff --git a/translations/es-ES/data/reusables/saml/saml-accounts.md b/translations/es-ES/data/reusables/saml/saml-accounts.md index bd4283168e..6c5482f9c1 100644 --- a/translations/es-ES/data/reusables/saml/saml-accounts.md +++ b/translations/es-ES/data/reusables/saml/saml-accounts.md @@ -1,7 +1,7 @@ -Si configuras el SSO de SAML, los miembros de tu organización seguirán ingresando en sus cuentas personales en {% data variables.product.prodname_dotcom_the_website %}. Cuando un miembro acceda a los recursos que no sean públicos dentro de tu organización y que utilicen el SSO de SAML, {% data variables.product.prodname_dotcom %} lo redireccionará a tu IdP para autenticarse. Después de autenticarse exitosamente, tu IdP redirecciona a este miembro a {% data variables.product.prodname_dotcom %}, en donde puede acceder a los recursos de tu organización. +If you configure SAML SSO, members of your organization will continue to sign into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}. When a member accesses non-public resources within your organization, {% data variables.product.prodname_dotcom %} redirects the member to your IdP to authenticate. After successful authentication, your IdP redirects the member back to {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Acerca de la autenticación con el inicio de sesión único de SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)". {% note %} -**Nota:** Los miembros organizacionales pueden realizar operaciones de lectura tales como ver, clonar y bifurcar los recursos públicos que pertenecen a tu organización, incluso si no tienen una sesión de SAML válida. +**Note:** SAML SSO does not replace the normal sign-in process for {% data variables.product.prodname_dotcom %}. Unless you use {% data variables.product.prodname_emus %}, members will continue to sign into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}, and each personal account will be linked to an external identity in your IdP. -{% endnote %} +{% endnote %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/secret-scanning/secret-list-private-push-protection.md b/translations/es-ES/data/reusables/secret-scanning/secret-list-private-push-protection.md index f27b9612ab..dbb8dba2ec 100644 --- a/translations/es-ES/data/reusables/secret-scanning/secret-list-private-push-protection.md +++ b/translations/es-ES/data/reusables/secret-scanning/secret-list-private-push-protection.md @@ -1,44 +1,17 @@ -| Proveedor | Secreto compatible | Tipo de secreto | -| ------------------------- | ------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | -| Adafruit IO | Clave de IO de Adafruit | adafruit_io_key | -| Alibaba Cloud | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_id
alibaba_cloud_access_key_secret | -| Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id
amazon_oauth_client_secret | -| Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key | aws_access_key_id
aws_secret_access_key | -| Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token
aws_temporary_access_key_id
aws_secret_access_key | -| Asana | Token de Acceso Personal de Asana | asana_personal_access_token | -| Atlassian | Token de Acceso Personal a Bitbucket Server | bitbucket_server_personal_access_token | -| Azure | Secreto de aplicación de Azure Active Directory | azure_active_directory_application_secret | -| Azure | Caché de Azure para la Llave de Acceso A Redis | azure_cache_for_redis_access_key | -| Azure | Token de Acceso Personal de Azure DevOps | azure_devops_personal_access_token | -| Checkout.com | Clave secreta de productión de Checkout.com | checkout_production_secret_key | -| Clojars | Token de Despliegue de Clojars | clojars_deploy_token | -| Databricks | Token de Acceso de Databricks | databricks_access_token | -| DigitalOcean | Token de Acceso Personal de DigitalOcean | digitalocean_personal_access_token | -| DigitalOcean | Token OAuth de DigitalOcean | digitalocean_oauth_token | -| DigitalOcean | Token de Actualización de DigitalOcean | digitalocean_refresh_token | -| DigitalOcean | Token de Sistema de DigitalOcean | digitalocean_system_token | -| Discord | Token de Bot de Discord | discord_bot_token | -| Doppler | Token Personal de Doppler | doppler_personal_token | -| Doppler | Token de Servicio de Doppler | doppler_service_token | -| Doppler | Token de CLI de Doppler | doppler_cli_token | -| Doppler | Token de SCIM de Doppler | doppler_scim_token | -| Doppler | Token de auditoría de Doppler | doppler_audit_token | -| Dropbox | Token de Acceso de Vida Corta de Dropbox | dropbox_short_lived_access_token | -| Duffel | Token de Acceso En Vivo para Duffel | duffel_live_access_token | -| EasyPost | Llave de la API de Producción de EasyPost | easypost_production_api_key | -| Flutterwave | Llave de Secreto de la API En Vivo de Flutterwave | flutterwave_live_api_secret_key | -| Fullstory | Llave de la API de FullStory | fullstory_api_key | -| GitHub | Token de Acceso Personal de GitHub | github_personal_access_token | -| GitHub | Token de Acceso de OAuth para GitHub | github_oauth_access_token | -| GitHub | Token de Actualización de GitHub | github_refresh_token | -| GitHub | Token de Acceso a la Instalación de GitHub App | github_app_installation_access_token | -| GitHub | Clave Privada de SSH de GitHub | github_ssh_private_key | -| Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id
google_cloud_storage_access_key_secret | -| Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id
google_cloud_storage_access_key_secret | -| Google | Google OAuth Client ID with Google OAuth Client Secret | google_oauth_client_id
google_oauth_client_secret | -| Grafana | Clave de la API de Grafana | grafana_api_key | -| Hubspot | Clave de API de Hubspot | hubspot_api_key | -| Intercom | Token de Acceso de Intercom | intercom_access_token | +| Proveedor | Secreto compatible | Tipo de secreto | +| ------------------------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | +| Adafruit IO | Clave de IO de Adafruit | adafruit_io_key | +| Alibaba Cloud | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_id
alibaba_cloud_access_key_secret | +| Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id
amazon_oauth_client_secret | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key | aws_access_key_id
aws_secret_access_key | +| Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token
aws_temporary_access_key_id
aws_secret_access_key | +| Asana | Token de Acceso Personal de Asana | asana_personal_access_token | +| Atlassian | Token de Acceso Personal a Bitbucket Server | bitbucket_server_personal_access_token | +| Azure | Secreto de aplicación de Azure Active Directory | azure_active_directory_application_secret | +| Azure | Caché de Azure para la Llave de Acceso A Redis | azure_cache_for_redis_access_key | +| Azure | Token de Acceso Personal de Azure DevOps | azure_devops_personal_access_token | +{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %} +Azure | Azure Storage Account Key | azure_storage_account_key{% endif %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key Clojars | Clojars Deploy Token | clojars_deploy_token Databricks | Databricks Access Token | databricks_access_token DigitalOcean | DigitalOcean Personal Access Token | digitalocean_personal_access_token DigitalOcean | DigitalOcean OAuth Token | digitalocean_oauth_token DigitalOcean | DigitalOcean Refresh Token | digitalocean_refresh_token DigitalOcean | DigitalOcean System Token | digitalocean_system_token Discord | Discord Bot Token | discord_bot_token Doppler | Doppler Personal Token | doppler_personal_token Doppler | Doppler Service Token | doppler_service_token Doppler | Doppler CLI Token | doppler_cli_token Doppler | Doppler SCIM Token | doppler_scim_token Doppler | Doppler Audit Token | doppler_audit_token Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token Duffel | Duffel Live Access Token | duffel_live_access_token EasyPost | EasyPost Production API Key | easypost_production_api_key Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key Fullstory | FullStory API Key | fullstory_api_key GitHub | GitHub Personal Access Token | github_personal_access_token GitHub | GitHub OAuth Access Token | github_oauth_access_token GitHub | GitHub Refresh Token | github_refresh_token GitHub | GitHub App Installation Access Token | github_app_installation_access_token GitHub | GitHub SSH Private Key | github_ssh_private_key Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id
google_cloud_storage_access_key_secret Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id
google_cloud_storage_access_key_secret Google | Google OAuth Client ID with Google OAuth Client Secret | google_oauth_client_id
google_oauth_client_secret Grafana | Grafana API Key | grafana_api_key Hubspot | Hubspot API Key | hubspot_api_key Intercom | Intercom Access Token | intercom_access_token {%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %} JFrog | Token de Acceso a la Plataforma de JFrog | jfrog_platform_access_token JFrog | Llave de la API de la Plataforma de JFrog | jfrog_platform_api_key{% endif %} Ionic | Token de Acceso personal a Ionic | ionic_personal_access_token Ionic | Token de Actualización de Ionic | ionic_refresh_token Linear | Llave de la API de Linear | linear_api_key Linear | Token de Acceso OAuth de Linear | linear_oauth_access_token Midtrans | Llave del Servidor de Producción de Midtrans | midtrans_production_server_key New Relic | Llave de la API Personal de New Relic | new_relic_personal_api_key New Relic | Llave de la API de REST de New Relic | new_relic_rest_api_key New Relic | Llave de Consulta de Perspectivas de New Relic | new_relic_insights_query_key npm | Token de Acceso a npm | npm_access_token NuGet | Llave de la API de NuGet | nuget_api_key Onfido | Token de la API en Vivo de Onfido | onfido_live_api_token OpenAI | Llave de la API de OpenAI | openai_api_key PlanetScale | Contraseña de la Base de Datos de PlanetScale | planetscale_database_password PlanetScale | Token OAuth de PlanetScale | planetscale_oauth_token PlanetScale | Token de Servicio de PlanetScale | planetscale_service_token Postman | Llave de la API de Postman | postman_api_key Proctorio | Llave del Secreto de Proctorio | proctorio_secret_key {%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %} diff --git a/translations/es-ES/data/reusables/security-overview/information-varies-GHAS.md b/translations/es-ES/data/reusables/security-overview/information-varies-GHAS.md new file mode 100644 index 0000000000..7d642c7fda --- /dev/null +++ b/translations/es-ES/data/reusables/security-overview/information-varies-GHAS.md @@ -0,0 +1,3 @@ +{% ifversion security-overview-displayed-alerts %} +The information shown in the security overview will vary according to your access to repositories, and on whether {% data variables.product.prodname_GH_advanced_security %} is used by those repositories. +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md index 73254d889d..54dce91ea3 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md @@ -36,4 +36,4 @@ shortTitle: Ownership continuity 3. [Successor settings] で後継者を招待し、ユーザ名、フルネーム、メールアドレスを入力して、名前が必要されたらそれをクリックします。 ![後継者招待の検索フィールド](/assets/images/help/settings/settings-invite-successor-search-field.png) 4. [**Add successor**] をクリックします。 {% data reusables.user-settings.sudo-mode-popup %} -5. 招待したユーザーは、後継者になることに合意するまで "Pending" としてリストされます。 ![後継者招待が Pending](/assets/images/help/settings/settings-pending-successor.png) +6. 招待したユーザーは、後継者になることに合意するまで "Pending" としてリストされます。 ![後継者招待が Pending](/assets/images/help/settings/settings-pending-successor.png) diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md index 941d889e9d..01aee641b7 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md @@ -32,7 +32,7 @@ shortTitle: 継続的インテグレーション ## {% data variables.product.prodname_actions %} を使用する継続的インテグレーションについて {% ifversion ghae %}{% data variables.product.prodname_actions %} を使用する CI は、リポジトリにコードをビルドしてテストを実行できるワークフローが利用できます。 Workflows can run on runner systems that you host. 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners)」を参照してください。 -{% else %}{% data variables.product.prodname_actions %} を利用した CI では、リポジトリ中のコードをビルドしてテストを実行できるワークフローが利用できます。 ワークフローは、{% data variables.product.prodname_dotcom %} でホストされている仮想マシン、または自分がホストしているマシンで実行できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} ホストランナーの仮想環境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)」および「[セルフホストランナーについて](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)」を参照してください。 +{% else %}{% data variables.product.prodname_actions %} を利用した CI では、リポジトリ中のコードをビルドしてテストを実行できるワークフローが利用できます。 ワークフローは、{% data variables.product.prodname_dotcom %} でホストされている仮想マシン、または自分がホストしているマシンで実行できます。 For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)." {% endif %} CIワークフローは、{% data variables.product.prodname_dotcom %}イベントが発生する (たとえば、新しいコードがリポジトリにプッシュされ) とき、または設定したスケジュールに応じて、あるいはリポジトリディスパッチwebhookを使用して外部イベントが発生するときに実行されるように設定することができます。 diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md index 5780a6fe0d..8b2cf5626e 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md @@ -28,8 +28,8 @@ shortTitle: Build & test Xamarin apps For a full list of available Xamarin SDK versions on the {% data variables.product.prodname_actions %}-hosted macOS runners, see the documentation: -* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles) -* [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles) +* [macOS 10.15](https://github.com/actions/runner-images/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles) +* [macOS 11](https://github.com/actions/runner-images/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles) {% data reusables.actions.macos-runner-preview %} diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md index 19e28b3dae..240ebbf8c3 100644 --- a/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md @@ -39,7 +39,7 @@ shortTitle: Docker container action {% ifversion ghae %} - 「[Docker コンテナファイルシステム](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)」 {% else %} -- [{% data variables.product.prodname_dotcom %}の仮想環境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners#docker-container-filesystem) +- "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)" {% endif %} 始める前に、{% data variables.product.prodname_dotcom %} リポジトリを作成する必要があります。 diff --git a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md index e252ca1561..c6fa4237a6 100644 --- a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -74,7 +74,7 @@ To access the environment variable in a Docker container action, you must pass t ### `inputs..required` -**必須** この入力パラメーターがアクションに必須かどうかを示す`論理値`。 パラメーターが必須の場合は`true`に設定してください。 +**Optional** A `boolean` to indicate whether the action requires the input parameter. パラメーターが必須の場合は`true`に設定してください。 ### `inputs..default` diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md index 316ebc58ae..d24fc59b63 100644 --- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md @@ -37,7 +37,7 @@ CircleCIから移行する際には、以下の差異を考慮してください - CircleCIの自動テストの並列性は、ユーザが指定したルールもしくは過去のタイミングの情報に基づいて、自動的にテストをグループ化します。 この機能は{% data variables.product.prodname_actions %}には組み込まれていません。 - コンテナはユーザのマッピングが異なるので、Dockerコンテナ内で実行されるアクションは、権限の問題に敏感です。 これらの問題の多くは、*Dockerfile*中で`USER`命令を使わなければ回避できます。 {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} -{% else %}{% data variables.product.product_name %}ホストランナー上の Docker のファイルシステムに関する詳しい情報については「[{% data variables.product.product_name %} ホストランナーの仮想環境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)」を参照してください。 +{% else %}For more information about the Docker filesystem on {% data variables.product.product_name %}-hosted runners, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)." {% endif %} ## ワークフローとジョブの移行 @@ -66,10 +66,10 @@ Docker ファイルシステムの詳細については、「[Docker コンテ {% data reusables.actions.self-hosted-runners-software %} {% else %} -Dockerのファイルシステムに関する詳しい情報については「[{% data variables.product.product_name %}ホストランナーの仮想環境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)」を参照してください。 +For more information about the Docker filesystem, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)." ー -{% data variables.product.prodname_dotcom %} ホストの仮想環境で使用できるツールとパッケージの詳細については、「[{% data variables.product.prodname_dotcom %} ホストランナーの仕様](/actions/reference/specifications-for-github-hosted-runners/#supported-software)」を参照してください。 +{% data variables.product.prodname_dotcom %}-hosted runner images, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". {% endif %} ## 変数とシークレットの利用 @@ -287,7 +287,8 @@ jobs: steps: # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. - # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem + # See https://docs.github.com/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem + - name: Setup file system permissions run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp - uses: {% data reusables.actions.action-checkout %} diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md index e83742f53b..e98483ae8a 100644 --- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md +++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md @@ -27,7 +27,7 @@ versions: ワークフローファイルで設定されたステップに加えて、{% data variables.product.prodname_dotcom %} はジョブの実行をセットアップして完了するために、各ジョブに 2 つの追加ステップを追加します。 これらのステップは、「Set up job」および「Complete job」として実行されるワークフローに記録されます。 -{% data variables.product.prodname_dotcom %}ホストランナー上のジョブの実行では、"Set up job"はランナーの仮想環境の詳細を記録し、ランナーマシン上にあったプリインストールされたツールのリストへのリンクを含みます。 +For jobs run on {% data variables.product.prodname_dotcom %}-hosted runners, "Set up job" records details of the runner image, and includes a link to the list of preinstalled tools that were present on the runner machine. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index eb6456168e..38cebfc663 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -105,18 +105,18 @@ macOS 仮想マシンのハードウェア仕様: {% data variables.product.prodname_dotcom %} ホストランナーに含まれているソフトウェアツールは毎週更新されます。 The update process takes several days, and the list of preinstalled software on the `main` branch is updated after the whole deployment ends. ### Preinstalled software -ワークフローログには、正確なランナーにプレインストールされているツールへのリンクが含まれています。 ワークフローログでこの情報を見つけるには、[`Set up job`] セクションを展開します。 そのセクションの下で、[`Virtual Environment`] セクションを展開します。 The link following `Included Software` will describe the preinstalled tools on the runner that ran the workflow. ![Installed software link](/assets/images/actions-runner-installed-software-link.png) 詳しい情報については、「[ワークフローの実行履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。 +ワークフローログには、正確なランナーにプレインストールされているツールへのリンクが含まれています。 ワークフローログでこの情報を見つけるには、[`Set up job`] セクションを展開します。 Under that section, expand the `Runner Image` section. The link following `Included Software` will describe the preinstalled tools on the runner that ran the workflow. ![Installed software link](/assets/images/actions-runner-installed-software-link.png) 詳しい情報については、「[ワークフローの実行履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。 For the overall list of included tools for each runner operating system, see the links below: -* [Ubuntu 22.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2204-Readme.md) -* [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-Readme.md) -* [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-Readme.md) -* [Windows Server 2022](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md) -* [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md) -* [macOS 12](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-12-Readme.md) -* [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md) -* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) +* [Ubuntu 22.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2204-Readme.md) +* [Ubuntu 20.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2004-Readme.md) +* [Ubuntu 18.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu1804-Readme.md) +* [Windows Server 2022](https://github.com/actions/runner-images/blob/main/images/win/Windows2022-Readme.md) +* [Windows Server 2019](https://github.com/actions/runner-images/blob/main/images/win/Windows2019-Readme.md) +* [macOS 12](https://github.com/actions/runner-images/blob/main/images/macos/macos-12-Readme.md) +* [macOS 11](https://github.com/actions/runner-images/blob/main/images/macos/macos-11-Readme.md) +* [macOS 10.15](https://github.com/actions/runner-images/blob/main/images/macos/macos-10.15-Readme.md) {% data variables.product.prodname_dotcom %}ホストランナーには、オペレーティングシステムのデフォルトの組み込みツールに加え、上のリファレンスのリスト内のパッケージにが含まれています。 たとえば、Ubuntu及びmacOSのランナーには、`grep`、`find`、`which`やその他のデフォルトのツールが含まれています。 @@ -126,7 +126,7 @@ For the overall list of included tools for each runner operating system, see the - アクションでは通常、バージョンの選択、引数を渡す機能、パラメータなどの機能が提供されています - これにより、ソフトウェアの更新に関係なく、ワークフローで使用されるツールのバージョンが同じままになります -リクエストしたいツールがある場合、[actions/virtual-environments](https://github.com/actions/virtual-environments) で Issue を開いてください。 このリポジトリには、ランナーに関するすべての主要なソフトウェア更新に関するお知らせも含まれています。 +If there is a tool that you'd like to request, please open an issue at [actions/runner-images](https://github.com/actions/runner-images). このリポジトリには、ランナーに関するすべての主要なソフトウェア更新に関するお知らせも含まれています。 ### Installing additional software diff --git a/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md b/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md index 4280d9e7de..cae3ee1894 100644 --- a/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md +++ b/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md @@ -20,7 +20,7 @@ miniTocMaxHeadingLevel: 3 ワークフローの実行は、しばしば他の実行と同じ出力あるいはダウンロードされた依存関係を再利用します。 たとえばMaven、Gradle、npm、Yarnといったパッケージ及び依存関係管理ツールは、ダウンロードされた依存関係のローカルキャッシュを保持します。 -{% ifversion fpt or ghec %} Jobs on {% data variables.product.prodname_dotcom %}-hosted runners start in a clean virtual environment and must download dependencies each time, causing increased network utilization, longer runtime, and increased cost. {% endif %}To help speed up the time it takes to recreate files like dependencies, {% data variables.product.prodname_dotcom %} can cache files you frequently use in workflows. +{% ifversion fpt or ghec %} Jobs on {% data variables.product.prodname_dotcom %}-hosted runners start in a clean runner image and must download dependencies each time, causing increased network utilization, longer runtime, and increased cost. {% endif %}To help speed up the time it takes to recreate files like dependencies, {% data variables.product.prodname_dotcom %} can cache files you frequently use in workflows. To cache dependencies for a job, you can use {% data variables.product.prodname_dotcom %}'s [`cache` action](https://github.com/actions/cache). The action creates and restores a cache identified by a unique key. Alternatively, if you are caching the package managers listed below, using their respective setup-* actions requires minimal configuration and will create and restore dependency caches for you. diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md index a47693dade..2dab1e7ae7 100644 --- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md @@ -146,7 +146,7 @@ Optionally, you can build custom tooling to automatically scale the self-hosted - "Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}" in the [{% data variables.product.prodname_ghe_server %}](/enterprise-server@latest/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect) or [{% data variables.product.prodname_ghe_managed %}](/github-ae@latest//admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect) documentation {%- endif %} -- You can customize the software available on your self-hosted runner machines, or configure your runners to run software similar to {% data variables.product.company_short %}-hosted runners{% ifversion ghes or ghae %} available for customers using {% data variables.product.prodname_dotcom_the_website %}{% endif %}. The software that powers runner machines for {% data variables.product.prodname_actions %} is open source. For more information, see the [`actions/runner`](https://github.com/actions/runner) and [`actions/virtual-environments`](https://github.com/actions/virtual-environments) repositories. +- You can customize the software available on your self-hosted runner machines, or configure your runners to run software similar to {% data variables.product.company_short %}-hosted runners{% ifversion ghes or ghae %} available for customers using {% data variables.product.prodname_dotcom_the_website %}{% endif %}. The software that powers runner machines for {% data variables.product.prodname_actions %} is open source. For more information, see the [`actions/runner`](https://github.com/actions/runner) and [`actions/runner-images`](https://github.com/actions/runner-images) repositories. ## 参考リンク diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index f19b8e5278..367ced039b 100644 --- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -30,7 +30,7 @@ You can populate the runner tool cache by running a {% data variables.product.pr {% note %} -**Note:** You can only use a {% data variables.product.prodname_dotcom %}-hosted runner's tool cache for a self-hosted runner that has an identical operating system and architecture. For example, if you are using a `ubuntu-18.04` {% data variables.product.prodname_dotcom %}-hosted runner to generate a tool cache, your self-hosted runner must be a 64-bit Ubuntu 18.04 machine. For more information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[Virtual environments for GitHub-hosted runners](/free-pro-team@latest/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)." +**Note:** You can only use a {% data variables.product.prodname_dotcom %}-hosted runner's tool cache for a self-hosted runner that has an identical operating system and architecture. For example, if you are using a `ubuntu-18.04` {% data variables.product.prodname_dotcom %}-hosted runner to generate a tool cache, your self-hosted runner must be a 64-bit Ubuntu 18.04 machine. For more information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/free-pro-team@latest/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)." {% endnote %} diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md index 042ecc2b2b..1308198d54 100644 --- a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md +++ b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md @@ -30,6 +30,8 @@ redirect_from: If your enterprise members manage their own user accounts on {% data variables.product.product_location %}, you can configure SAML authentication as an additional access restriction for your enterprise or organization. {% data reusables.saml.dotcom-saml-explanation %} +{% data reusables.saml.saml-accounts %} + {% data reusables.saml.about-saml-enterprise-accounts %}詳しい情報については、「[Enterprise 向けの SAML シングルサインオンを設定する](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)」を参照してください。 Alternatively, you can provision and manage the accounts of your enterprise members with {% data variables.product.prodname_emus %}. To help you determine whether SAML SSO or {% data variables.product.prodname_emus %} is better for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)." diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md index 228e1477c0..1d5f052d14 100644 --- a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md @@ -29,7 +29,11 @@ redirect_from: {% ifversion ghec %} -{% data reusables.saml.dotcom-saml-explanation %} 詳細は「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)」を参照してください。 +{% data reusables.saml.dotcom-saml-explanation %} + +{% data reusables.saml.saml-accounts %} + +For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." {% data reusables.saml.about-saml-enterprise-accounts %} diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index bb1cdd3ba2..7e0c84eedc 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -418,13 +418,13 @@ Before you'll see `git` category actions, you must enable Git events in the audi ## `integration_installation`category actions -| アクション | 説明 | -| ------------------------------------------------ | ----------------------------------------------- | -| `integration_installation.contact_email_changed` | A contact email for an integration was changed. | -| `integration_installation.create` | An integration was installed. | -| `integration_installation.destroy` | An integration was uninstalled. | -| `integration_installation.repositories_added` | Repositories were added to an integration. | -| `integration_installation.repositories_removed` | Repositories were removed from an integration. | +| アクション | 説明 | +| ------------------------------------------------ | ------------------------- | +| `integration_installation.contact_email_changed` | インテグレーションの連絡先メールが変更されました。 | +| `integration_installation.create` | インテグレーションがインストールされました。 | +| `integration_installation.destroy` | インテグレーションがアンインストールされました。 | +| `integration_installation.repositories_added` | インテグレーションにリポジトリが追加されました。 | +| `integration_installation.repositories_removed` | インテグレーションからリポジトリが削除されました。 | {%- ifversion fpt or ghec %} | `integration_installation.suspend` | An integration was suspended. | `integration_installation.unsuspend` | An integration was unsuspended. {%- endif %} diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md index d5240df0e0..37ce5c99c0 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md @@ -14,12 +14,6 @@ topics: - Security --- -{% note %} - -**Note:** Display of IP addresses in the enterprise audit log is currently in public beta and is subject to change. - -{% endnote %} - ## About display of IP addresses in the audit log By default, {% data variables.product.product_name %} does not display the source IP address for events in your enterprise's audit log. Optionally, to ensure compliance and respond to threats, you can display the full IP address associated with the actor responsible for each event. Actors are typically users, but can also be apps or integrations. diff --git a/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md b/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md index ce0b3dfeef..38233a46b1 100644 --- a/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md +++ b/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md @@ -35,14 +35,14 @@ The enterprise account on {% ifversion ghes %}{% data variables.product.product_ Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. 詳細は「[Organization について](/organizations/collaborating-with-groups-in-organizations/about-organizations)」を参照してください。 {% ifversion ghec %} -Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings. +Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings. 詳しい情報については「[EnterpriseへのOrganizationの追加](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)」を参照してください。 {% endif %} Your enterprise account allows you to manage and enforce policies for all the organizations owned by the enterprise. {% data reusables.enterprise.about-policies %} For more information, see "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)." {% ifversion ghec %} -{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." +{% data reusables.enterprise.create-an-enterprise-account %} 詳しい情報については「[Enterpriseアカウントの作成](/admin/overview/creating-an-enterprise-account)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md index 06a647f299..ed361ffe3c 100644 --- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md @@ -14,15 +14,16 @@ topics: - Enterprise - Organizations shortTitle: Add organizations +permissions: Enterprise owners can add organizations to an enterprise. --- ## Organizationについて Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. 詳細は「[Organization について](/organizations/collaborating-with-groups-in-organizations/about-organizations)」を参照してください。 -Enterprise owners can create new organizations within an enterprise account's settings or invite existing organizations to join an enterprise. To add an organization to your enterprise, you must create the organization from within the enterprise account settings. +You can add a new or existing organization to your enterprise in your enterprise account's settings. -You can only add organizations this way to an existing enterprise account. {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." +You can only add organizations this way to an existing enterprise account. {% data reusables.enterprise.create-an-enterprise-account %} 詳しい情報については「[Enterpriseアカウントの作成](/admin/overview/creating-an-enterprise-account)」を参照してください。 ## Enterprise アカウント内で Organization を作成する diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md index 0c85dd65ca..cc5bc9e133 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md @@ -50,9 +50,11 @@ fatal: The remote end hung up unexpectedly ## SSH キーを追加する -新規ユーザは、SSHキーを追加する際にパスワードを要求されます。 +{% ifversion ghes %} -![パスワードの確認](/assets/images/help/settings/sudo_mode_popup.png) +When a new user adds an SSH key to an account, to confirm the user's access, {% data variables.product.product_name %} will prompt for authentication. For more information, see "[Sudo mode](/authentication/keeping-your-account-and-data-secure/sudo-mode)." + +{% endif %} ユーザがキーを追加したら、次のような通知メールが届きます。 diff --git a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index fddbc48cd8..4ddcce7730 100644 --- a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: SAMLのシングルサインオンでの認証について -intro: 'You can access {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% ifversion ghec %} After you authenticate with the IdP successfully from {% data variables.product.product_name %}, you must authorize any personal access token, SSH key, or {% data variables.product.prodname_oauth_app %} you would like to access the organization''s resources.{% endif %}' +intro: 'You can access {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).' redirect_from: - /articles/about-authentication-with-saml-single-sign-on - /github/authenticating-to-github/about-authentication-with-saml-single-sign-on @@ -29,10 +29,9 @@ SAML SSO を使用すると、Enterprise のオーナーは、SAML IdP から {% {% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your personal account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}. -If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will use a new account that is provisioned for you. {% data reusables.enterprise-accounts.emu-more-info-account %} +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will instead use a new account that is provisioned for you and controlled by your enterprise. {% data reusables.enterprise-accounts.emu-more-info-account %} - -SAML SSO を使用する Organization のリソースにアクセスすると、{% data variables.product.prodname_dotcom %}は認証のために Organization の SAML IdP にリダイレクトします。 IdP でアカウントが正常に認証されると、IdP は{% data variables.product.prodname_dotcom %}に戻り、Organization のリソースにアクセスできます。 +When you access private resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. IdP でアカウントが正常に認証されると、IdP は{% data variables.product.prodname_dotcom %}に戻り、Organization のリソースにアクセスできます。 {% data reusables.saml.outside-collaborators-exemption %} @@ -40,6 +39,16 @@ SAML SSO を使用する Organization のリソースにアクセスすると、 {% data reusables.saml.you-must-periodically-authenticate %} +## Linked SAML identities + +When you authenticate with your IdP account and return to {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_dotcom %} will record a link in the organization or enterprise between your {% data variables.product.prodname_dotcom %} personal account and the SAML identity you signed into. This linked identity is used to validate your membership in that organization, and depending on your organization or enterprise setup, is also used to determine which organizations and teams you're a member of as well. Each {% data variables.product.prodname_dotcom %} account can be linked to exactly one SAML identity per organization. Likewise, each SAML identity can be linked to exactly one {% data variables.product.prodname_dotcom %} account in an organization. + +If you sign in with a SAML identity that is already linked to another {% data variables.product.prodname_dotcom %} account, you will receive an error message indicating that you cannot sign in with that SAML identity. This situation can occur if you are attempting to use a new {% data variables.product.prodname_dotcom %} account to work inside of your organization. If you didn't intend to use that SAML identity with that {% data variables.product.prodname_dotcom %} account, then you'll need to sign out of that SAML identity and then repeat the SAML login. If you do want to use that SAML identity with your {% data variables.product.prodname_dotcom %} account, you'll need to ask your admin to unlink your SAML identity from your old account, so that you can link it to your new account. Depending on the setup of your organization or enterprise, your admin may also need to reassign your identity within your SAML provider. 詳細は、「[Organizationへのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)」を参照してください。 + +If the SAML identity you sign in with does not match the SAML identity that is currently linked to your {% data variables.product.prodname_dotcom %} account, you'll receive a warning that you are about to relink your account. Because your SAML identity is used to govern access and team membership, continuing with the new SAML identity can cause you to lose access to teams and organizations inside of {% data variables.product.prodname_dotcom %}. Only continue if you know that you're supposed to use that new SAML identity for authentication in the future. + +## Authorizing PATs and SSH keys with SAML SSO + SAML SSL を要求する Organization 内の保護されたコンテンツにアクセスするために API またはコマンドライン上の Git を利用するには、認可された個人のアクセストークンを HTTPS 経由で使うか、認可された SSH キーを使う必要があります。 個人のアクセストークンあるいは SSH キーを持っていない場合、コマンドライン用の個人のアクセストークンを作成するか、新しい SSH キーを生成できます。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」または「[新しい SSH キーを生成して ssh-agent へ追加する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)」を参照してください。 @@ -58,5 +67,5 @@ To see the {% data variables.product.prodname_oauth_apps %} you've authorized, v ## 参考リンク -{% ifversion ghec %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} -{% ifversion ghae %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} +{% ifversion ghec %}- 「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)」{% endif %} +{% ifversion ghae %}- 「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/admin/authentication/about-identity-and-access-management-for-your-enterprise)」{% endif %} diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md index e64b6f397c..5293b50d56 100644 --- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md +++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md @@ -14,8 +14,6 @@ topics: - SSH --- -## SSH について - {% data reusables.ssh.about-ssh %} For more information about SSH, see [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) on Wikipedia. When you set up SSH, you will need to generate a new private SSH key and add it to the SSH agent. You must also add the public SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)." diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md index e00b4bd018..06825e0163 100644 --- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md @@ -90,7 +90,7 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab 5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば、個人のMacを使っているなら、このキーを「Personal MacBook Air」とすることができるでしょう。 6. キーを [Key] フィールドに貼り付けます。 ![キーフィールド](/assets/images/help/settings/ssh-key-paste.png) 7. **[Add SSH key]** をクリックしてください。 ![キーの追加ボタン](/assets/images/help/settings/ssh-add-key.png) -8. {% data variables.product.product_name %} パスワードの確認を促された場合は、確認します。 ![sudo モードダイアログ](/assets/images/help/settings/sudo_mode_popup.png) +{% data reusables.user-settings.sudo-mode-popup %} {% endwebui %} @@ -122,7 +122,7 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab 5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば、個人のMacを使っているなら、このキーを「Personal MacBook Air」とすることができるでしょう。 6. キーを [Key] フィールドに貼り付けます。 ![キーフィールド](/assets/images/help/settings/ssh-key-paste.png) 7. **[Add SSH key]** をクリックしてください。 ![キーの追加ボタン](/assets/images/help/settings/ssh-add-key.png) -8. {% data variables.product.product_name %} パスワードの確認を促された場合は、確認します。 ![sudo モードダイアログ](/assets/images/help/settings/sudo_mode_popup.png) +{% data reusables.user-settings.sudo-mode-popup %} {% endwebui %} diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md index 59f3c82976..7232bec404 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md @@ -1,6 +1,6 @@ --- title: Sudo モード -intro: '{% data variables.product.product_name %} は、メールアドレスの修正、第三者のアプリケーションの許可や新しい公開鍵の追加前、または、sudo でプロテクトされたアクションを開始する前に、パスワードを尋ねます。' +intro: 'To confirm access to your account before you perform a potentially sensitive action, {% data variables.product.product_location %} prompts for authentication.' redirect_from: - /articles/sudo-mode - /github/authenticating-to-github/sudo-mode @@ -9,15 +9,86 @@ versions: fpt: '*' ghes: '*' ghec: '*' +miniTocMaxHeadingLevel: 3 topics: - Identity - Access management --- -sudoでプロテクトされたアクションを実行したあとは、数時間アクションがない場合に限り、再認証を要求されます。 Sudo でプロテクトされたアクションを行った場合、このタイマーはリセットされます。 +## About sudo mode -![Sudo モードダイアログ](/assets/images/help/settings/sudo_mode_popup.png) +To maintain the security of your account when you perform a potentially sensitive action on {% data variables.product.product_location %}, you must authenticate even though you're already signed in. For example, {% data variables.product.company_short %} considers the following actions sensitive because each action could allow a new person or system to access your account. -## 参考リンク +- Modification of an associated email address +- Authorization of a third-party application +- Addition of a new SSH key -- [Unix `sudo` コマンド](http://en.wikipedia.org/wiki/Sudo) +After you authenticate to perform a sensitive action, your session is temporarily in "sudo mode." In sudo mode, you can perform sensitive actions without authentication. {% data variables.product.product_name %} will wait a few hours before prompting you for authentication again. During this time, any sensitive action that you perform will reset the timer. + +{% ifversion ghes %} + +{% note %} + +**Note**: If {% data variables.product.product_location %} uses an external authentication method like CAS or SAML SSO, you will not receive prompts to enter sudo mode. 詳しい情報については、サイト管理者にお問い合わせください。 + +{% endnote %} + +{% endif %} + +"sudo" is a reference to a program on Unix systems, where the name is short for "**su**peruser **do**." For more information, see [sudo](https://wikipedia.org/wiki/Sudo) on Wikipedia. + +## Confirming access for sudo mode + +To confirm access for sudo mode, you {% ifversion totp-and-mobile-sudo-challenge %}can{% else %}must{% endif %} authenticate with your password.{% ifversion totp-and-mobile-sudo-challenge %} Optionally, you can use a different authentication method, like {% ifversion fpt or ghec %}a security key, {% data variables.product.prodname_mobile %}, or a 2FA code{% elsif ghes %}a security key or a 2FA code{% endif %}.{% endif %} + +{% ifversion totp-and-mobile-sudo-challenge %} +- [Confirming access using a security key](#confirming-access-using-a-security-key) +{%- ifversion fpt or ghec %} +- [Confirming access using GitHub Mobile](#confirming-access-using-github-mobile) +{%- endif %} +- [Confirming access using a 2FA code](#confirming-access-using-a-2fa-code) +- [Confirming access using your password](#confirming-access-using-your-password) + +### Confirming access using a security key + +You must configure two-factor authentication (2FA) for your account using a security key to confirm access to your account for sudo mode using the security key. 詳しい情報については、「[2 要素認証を設定する](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)」を参照してください。 + +When prompted to authenticate for sudo mode, click **Use security key**, then follow the prompts. + +![Screenshot of security key option for sudo mode](/assets/images/help/settings/sudo_mode_prompt_security_key.png) + +{% endif %} + +{% ifversion fpt or ghec %} + +### Confirming access using {% data variables.product.prodname_mobile %} + +You must install and sign into {% data variables.product.prodname_mobile %} to confirm access to your account for sudo mode using the app. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)." + +1. When prompted to authenticate for sudo mode, click **Use GitHub Mobile**. + + ![Screenshot of {% data variables.product.prodname_mobile %} option for sudo mode](/assets/images/help/settings/sudo_mode_prompt_github_mobile_prompt.png) +1. Open {% data variables.product.prodname_mobile %}. {% data variables.product.prodname_mobile %} will display numbers that you must enter on {% data variables.product.product_location %} to approve the request. + + ![Screenshot of numbers from {% data variables.product.prodname_mobile %} to enter on {% data variables.product.product_name %} to approve sudo mode access](/assets/images/help/settings/sudo_mode_prompt_github_mobile.png) +1. On {% data variables.product.product_name %}, type the numbers displayed in {% data variables.product.prodname_mobile %}. + +{% endif %} + +{% ifversion totp-and-mobile-sudo-challenge %} + +### Confirming access using a 2FA code + +You must configure 2FA using a TOTP mobile app{% ifversion fpt or ghec %} or text messages{% endif %} to confirm access to your account for sudo mode using a 2FA code. 詳しい情報については、「[2 要素認証を設定する](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)」を参照してください。 + +When prompted to authenticate for sudo mode, type the authentication code from your TOTP mobile app{% ifversion fpt or ghec %} or the text message{% endif %}, then click **Verify**. + +![Screenshot of 2FA code prompt for sudo mode](/assets/images/help/settings/sudo_mode_prompt_2fa_code.png) + +### Confirming access using your password + +{% endif %} + +When prompted to authenticate for sudo mode, type your password, then click **Confirm**. + +![Screenshot of password prompt for sudo mode](/assets/images/help/settings/sudo_mode_prompt_password.png) diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md index c6c10d3caf..4e61ee5158 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md @@ -25,14 +25,18 @@ shortTitle: Update access credentials ![Password reset email request dialog](/assets/images/help/settings/password-recovery-email-request.png) 3. We'll email you a link that will allow you to reset your password. You must click on this link within 3 hours of receiving the email. If you didn't receive an email from us, make sure to check your spam folder. 4. If you have enabled two-factor authentication, you will be prompted for your 2FA credentials: +{% ifversion fpt or ghec %} * If you have {% data variables.product.prodname_mobile %}, you will be sent a push notification to verify your identity. Open the push notification or the {% data variables.product.prodname_mobile %} app and enter the two-digit code shown to you on the password reset page in your browser. ![Two-factor {% data variables.product.prodname_mobile %} authentication prompt](/assets/images/help/2fa/2fa-mobile-challenge-password-reset.png) * To skip using GitHub Mobile to verify, click **Enter two-factor authentication or recovery code**. ![Two-factor GitHub Mobile authentication prompt on {% data variables.product.product_name %} with "Enter two-factor authentication or recovery code" highlighted](/assets/images/help/2fa/2fa-github-mobile-password-reset.png) +{% endif %} * Type your authentication code or one of your recovery codes and click **Verify**. ![Two-factor authentication prompt](/assets/images/help/2fa/2fa-password-reset.png) * If you have added a security key to your account, click **Use security key** instead of typing an authentication code. + {% ifversion fpt or ghec %} * If you have set up [{% data variables.product.prodname_mobile %}](https://github.com/mobile), click **Authenticate with GitHub Mobile** instead. + {% endif %} 5. Type a new password, confirm your new password, and click **Change password**. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)." {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %} ![Password recovery box](/assets/images/enterprise/settings/password-recovery-page.png){% endif %} diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md index 729a1e93f7..686a099b7b 100644 --- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md +++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md @@ -34,11 +34,11 @@ topics: ## 依存関係 -使用しているコンテナで特定の依存関係がない場合 (たとえば、Git は PATH 変数にインストールされ、追加されている必要がある)、{% data variables.product.prodname_code_scanning %} を実行する上で困難が生じる場合があります。 依存関係の問題が生じた場合は、{% data variables.product.prodname_dotcom %} の仮想環境に通常含まれているソフトウェアのリストを確認してください。 詳しい情報については、次の場所にある特定のバージョンの `readme` ファイルを参照してください。 +使用しているコンテナで特定の依存関係がない場合 (たとえば、Git は PATH 変数にインストールされ、追加されている必要がある)、{% data variables.product.prodname_code_scanning %} を実行する上で困難が生じる場合があります。 依存関係の問題が生じた場合は、通常{% data variables.product.prodname_dotcom %}のランナーのイメージに含まれているソフトウェアのリストをレビューしてください。 詳しい情報については、次の場所にある特定のバージョンの `readme` ファイルを参照してください。 -* Linux: https://github.com/actions/virtual-environments/tree/main/images/linux -* macOS: https://github.com/actions/virtual-environments/tree/main/images/macos -* Windows: https://github.com/actions/virtual-environments/tree/main/images/win +* Linux: https://github.com/actions/runner-images/tree/main/images/linux +* macOS: https://github.com/actions/runner-images/tree/main/images/macos +* Windows: https://github.com/actions/runner-images/tree/main/images/win ## ワークフローの例 diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index c900d9dfe1..5bbb673719 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -88,7 +88,7 @@ For repositories where {% data variables.product.prodname_dependabot_security_up ## Access to {% data variables.product.prodname_dependabot_alerts %} -You can see all of the alerts that affect a particular project{% ifversion fpt or ghec %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)." +You can see all of the alerts that affect a particular project{% ifversion fpt or ghec %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)." By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} never publicly discloses insecure dependencies for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working with repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." {% endif %} @@ -102,5 +102,5 @@ You can also see all the {% data variables.product.prodname_dependabot_alerts %} ## Further reading - "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" -- "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} {% ifversion fpt or ghec %}- "[Privacy on {% data variables.product.prodname_dotcom %}](/get-started/privacy-on-github)"{% endif %} diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md index b94ae151ca..0344ac5067 100644 --- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -93,7 +93,7 @@ You can configure {% data variables.product.prodname_dependabot %} to ignore spe ## Further reading - "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" -- "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" - "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes > 3.2 %} - "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/translations/ja-JP/content/code-security/getting-started/github-security-features.md b/translations/ja-JP/content/code-security/getting-started/github-security-features.md index 19978f53ae..bc033f52bd 100644 --- a/translations/ja-JP/content/code-security/getting-started/github-security-features.md +++ b/translations/ja-JP/content/code-security/getting-started/github-security-features.md @@ -58,8 +58,15 @@ The dependency graph allows you to explore the ecosystems and packages that your You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +{% ifversion security-overview-displayed-alerts %} +### Security overview + +The security overview allows you to review security configurations and alerts, making it easy to identify the repositories and organizations at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + +{% else %} ### Security overview for repositories -For all public repositories, the security overview shows which security features are enabled for the repository, and offers the option to configure any available security features that are not currently enabled. +The security overview shows which security features are enabled for the repository, and offers you the option of configuring any available security features that are not already enabled. +{% endif %} ## Available with {% data variables.product.prodname_GH_advanced_security %} @@ -67,7 +74,7 @@ For all public repositories, the security overview shows which security features The following {% data variables.product.prodname_GH_advanced_security %} features are available and free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can use the full set of features in any of their repositories. For a list of the features available with {% data variables.product.prodname_ghe_cloud %}, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/github-security-features#available-with-github-advanced-security). {% elsif ghec %} -Many {% data variables.product.prodname_GH_advanced_security %} features are available and free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations within an enterprise that has a {% data variables.product.prodname_GH_advanced_security %} license can use all the following features on their repositories. {% data reusables.advanced-security.more-info-ghas %} +Many {% data variables.product.prodname_GH_advanced_security %} features are available and free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations within an enterprise that have a {% data variables.product.prodname_GH_advanced_security %} license can use the following features on all their repositories. {% data reusables.advanced-security.more-info-ghas %} {% elsif ghes %} {% data variables.product.prodname_GH_advanced_security %} features are available for enterprises with a license for {% data variables.product.prodname_GH_advanced_security %}. The features are restricted to repositories owned by an organization. {% data reusables.advanced-security.more-info-ghas %} @@ -86,7 +93,7 @@ Automatically detect security vulnerabilities and coding errors in new or modifi Automatically detect leaked secrets across all public repositories. {% data variables.product.company_short %} informs the relevant service provider that the secret may be compromised. For details of the supported secrets and service providers, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)." {% endif %} -{% ifversion not fpt %} +{% ifversion ghec or ghes or ghae %} ### {% data variables.product.prodname_secret_scanning_GHAS_caps %} {% ifversion ghec %} @@ -100,12 +107,12 @@ Automatically detect tokens or credentials that have been checked into a reposit Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." -{% ifversion ghec or ghes or ghae %} -### Security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %}, enterprises,{% endif %} and teams +{% ifversion security-overview-displayed-alerts %} -{% ifversion ghec %} -Available only with a license for {% data variables.product.prodname_GH_advanced_security %}. -{% endif %} +{% elsif fpt %} + +{% else %} +### Security overview for organizations{% ifversion ghes > 3.4 or ghae-issue-6199 %}, enterprises,{% endif %} and teams Review the security configuration and alerts for your organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." {% endif %} diff --git a/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md b/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md index 155ef044ab..e560122037 100644 --- a/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md +++ b/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md @@ -123,7 +123,7 @@ For more information, see "[Managing security and analysis settings for your org {% data variables.product.prodname_code_scanning_capc %} is configured at the repository level. 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)." ## Next steps -You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." {% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} diff --git a/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md b/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md index 9d2fbc8235..ec95d618b2 100644 --- a/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md +++ b/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md @@ -132,7 +132,7 @@ You can set up {% data variables.product.prodname_code_scanning %} to automatica {% endif %} ## Next steps -You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." {% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} diff --git a/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md b/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md index d6d8def31e..481ec138e4 100644 --- a/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md +++ b/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md @@ -91,7 +91,7 @@ For more information about viewing and resolving {% data variables.product.prodn Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." -{% ifversion ghec or ghes %} +{% ifversion ghec or ghes or ghae-issue-5503 %} You can use the security overview to see an organization-level view of which repositories have enabled {% data variables.product.prodname_secret_scanning %} and the alerts found. For more information, see "[Viewing the security overview](/code-security/security-overview/viewing-the-security-overview)." {% endif %} diff --git a/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md b/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md index d3f602193d..ba90d98e13 100644 --- a/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md @@ -43,7 +43,7 @@ In the security overview, you can view, sort, and filter alerts to understand th {% ifversion security-overview-views %} -In the security overview, at both the organization and repository level, there are dedicated views for specific security features, such as secret scanning alerts and code scanning alerts. You can use these views to limit your analysis to a specific set of alerts, and narrow the results further with a range of filters specific to each view. For example, in the secret scanning alert view, you can use the `Secret type` filter to view only secret scanning alerts for a specific secret, like a GitHub Personal Access Token. At the repository level, you can use the security overview to assess the specific repository's current security status, and configure any additional security features not yet in use on the repository. +In the security overview, there are dedicated views for each type of security alert, such as Dependabot, code scanning, and secret scanning alerts. You can use these views to limit your analysis to a specific set of alerts, and narrow the results further with a range of filters specific to each view. For example, in the secret scanning alert view, you can use the `Secret type` filter to view only secret scanning alerts for a specific secret, like a GitHub Personal Access Token. At the repository level, you can use the security overview to assess the specific repository's current security status, and configure any additional security features not yet in use on the repository. {% endif %} diff --git a/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md index 6c427b0e8a..1d6e0dba3a 100644 --- a/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md +++ b/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md @@ -25,6 +25,10 @@ shortTitle: アラートのフィルタリング アラートのリスクレベル、アラートの種類、機能の有効化の状況といった様々な要素に基づいて焦点を絞り込むために、セキュリティの概要でフィルタを利用できます。 特定のビューや、分析がOrganization、Team、リポジトリのレベルなのかといったことに応じて、様々なフィルタが利用できます。 +{% note %} +{% data reusables.security-overview.information-varies-GHAS %} +{% endnote %} + ## リポジトリでフィルタリング すべてのOrganizationレベル及びTeamレベルのビューで利用可能。 diff --git a/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md b/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md index e371b12dfc..728958e1ac 100644 --- a/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md +++ b/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md @@ -21,6 +21,8 @@ shortTitle: セキュリティの概要の表示 {% data reusables.security-overview.beta %} {% endif %} +{% data reusables.security-overview.information-varies-GHAS %} + ## Organizationのセキュリティの概要の表示 {% data reusables.organizations.navigate-to-org %} diff --git a/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md b/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md index c381e02761..00e0bc5440 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md @@ -34,7 +34,7 @@ topics: 3. 侵害されたビルドが将来のビルドに影響し続けることがないよう、各ビルドは新しい環境で開始されなければなりません。 -{% data variables.product.prodname_actions %}は、これらの機能を満たすのに役立ちます。 ビルドの手順は、コードとともにリポジトリに保存されます。 ビルドが実行される環境は、Windows、Mac、Linux、自分でホストするランナーを含め、選択できます。 各ビルドは新しい仮想環境で開始され、攻撃がビルド環境に留まり続けるのを難しくします。 +{% data variables.product.prodname_actions %}は、これらの機能を満たすのに役立ちます。 ビルドの手順は、コードとともにリポジトリに保存されます。 ビルドが実行される環境は、Windows、Mac、Linux、自分でホストするランナーを含め、選択できます。 各ビルドは新しいランナーのイメージで開始され、攻撃がビルド環境に留まり続けるのを難しくします。 セキュリティ上の利点に加えて、{% data variables.product.prodname_actions %}はビルドを手動、定期的、リポジトリでのgitイベントでトリガーし、頻繁に高速なビルドを行えます。 diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index d5b1211fe0..172d711d88 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -110,7 +110,7 @@ Dependency submission API（ベータ）を使ってプロジェクトにサブ ## 参考リンク - [依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph) -- 「[{% data variables.product.prodname_dependabot_alerts %}の表示と更新](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)」{% ifversion ghec %} +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% ifversion ghec %} - 「[Organizationのインサイトの表示](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)」{% endif %}{% ifversion fpt or ghec %} - [{% data variables.product.prodname_dotcom %}によるデータの利用と保護の方法の理解](/get-started/privacy-on-github) {% endif %} diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md index 668ab35ee1..d4164f266b 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md @@ -138,22 +138,18 @@ To create a new codespace, use the `gh codespace create` subcommand. gh codespace create ``` -You are prompted to choose a repository, a branch, and a machine type (if more than one is available). - -{% note %} - -**ノート**: 現在、{% data variables.product.prodname_cli %}ではcodespaceの作成時に開発コンテナの設定を選択することはできません。 特定の開発コンテナの設定を選択したい場合、{% data variables.product.prodname_dotcom %} Webインターフェースを使ってcodespaceを作成してください。 For more information, click the "Web browser" tab at the top of this page. - -{% endnote %} +You are prompted to choose a repository, a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available). Alternatively, you can use flags to specify some or all of the options: ```shell -gh codespace create -r owner/repo -b branch -m machine-type +gh codespace create -r owner/repo -b branch --devcontainer-path path -m machine-type ``` In this example, replace `owner/repo` with the repository identifier. Replace `branch` with the name of the branch, or the full SHA hash of the commit, that you want to be initially checked out in the codespace. If you use the `-r` flag without the `b` flag, the codespace is created from the default branch. +Replace `path` with the path to the dev container configuration file you want to use for the new codespace. If you omit this flag and more than one dev container file is available you will be prompted to choose one from a list. For more information about the dev container configuration file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." + Replace `machine-type` with a valid identifier for an available machine type. Identifiers are strings such as: `basicLinux32gb` and `standardLinux32gb`. The type of machines that are available depends on the repository, your personal account, and your location. If you enter an invalid or unavailable machine type, the available types are shown in the error message. If you omit this flag and more than one machine type is available you will be prompted to choose one from a list. For full details of the options for this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_create). diff --git a/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md index ec6b3b6496..f2774b816b 100644 --- a/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md @@ -32,38 +32,28 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th - **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." -{% ifversion ghec or ghes %} +{% ifversion ghes < 3.7 or ghae %} + - **Security overview** - Review the security configuration and alerts for an organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." {% endif %} {% ifversion fpt or ghec %} The table below summarizes the availability of {% data variables.product.prodname_GH_advanced_security %} features for public and private repositories. -{% ifversion fpt %} | | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} | | :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: | | Code scanning | Yes | No | Yes | | Secret scanning | Yes **(limited functionality only)** | No | Yes | | Dependency review | Yes | No | Yes | -{% endif %} -{% ifversion ghec %} -| | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} | -| :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: | -| Code scanning | Yes | No | Yes | -| Secret scanning | Yes **(limited functionality only)** | No | Yes | -| Dependency review | Yes | No | Yes | -| Security overview | No | No | Yes | -{% endif %} - {% endif %} For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." For an overview of all security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." {% ifversion fpt or ghec %} -{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% ifversion ghec %}, except for the security overview{% endif %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access to an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} +{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} {% endif %} -{% ifversion ghes > 3.1 or ghec %} +{% ifversion ghes > 3.1 or ghec or ghae %} ## Deploying GitHub Advanced Security in your enterprise To learn about what you need to know to plan your {% data variables.product.prodname_GH_advanced_security %} deployment at a high level and to review the rollout phases we recommended, see "[Adopting {% data variables.product.prodname_GH_advanced_security %} at scale](/code-security/adopting-github-advanced-security-at-scale)." diff --git a/translations/ja-JP/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md b/translations/ja-JP/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md index b8025330c8..3b257f4052 100644 --- a/translations/ja-JP/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md +++ b/translations/ja-JP/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md @@ -45,5 +45,5 @@ When you enable data use for your private repository, you'll be able to access t ## Further reading - "[About {% data variables.product.prodname_dotcom %}'s use of your data](/articles/about-github-s-use-of-your-data)" -- "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" diff --git a/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md b/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md index 3b5693c44b..3c1e663c39 100644 --- a/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md @@ -33,7 +33,6 @@ GraphQLサーバーと通信するには、適切なスコープを持つOAuth ``` repo -repo_deployment read:packages read:org read:public_key diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md index 85aefe6a1f..808fa924cd 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md @@ -1,7 +1,7 @@ --- -title: 'Planning and tracking with {% data variables.product.prodname_projects_v2 %}' +title: '{% data variables.product.prodname_projects_v2 %}での計画と追跡' shortTitle: '{% data variables.product.prodname_projects_v2 %}' -intro: 'Build adaptable projects to track your work on {% data variables.product.company_short %}.' +intro: '{% data variables.product.company_short %}での作業を追跡するために、適応性のあるプロジェクトを構築してください。' versions: feature: projects-v2 topics: diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md index 984016d45d..23db9c4d98 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md @@ -1,6 +1,6 @@ --- title: '{% data variables.product.prodname_projects_v2 %}について' -intro: '{% data variables.product.prodname_projects_v2 %} is an adaptable, flexible tool for planning and tracking work on {% data variables.product.company_short %}.' +intro: '{% data variables.product.prodname_projects_v2 %}は、{% data variables.product.company_short %}上の作業の計画と追跡のための、適応性のある柔軟なツールです。' allowTitleToDifferFromFilename: true miniTocMaxHeadingLevel: 3 versions: @@ -14,25 +14,25 @@ topics: ## {% data variables.product.prodname_projects_v2 %}について -A project is an adaptable spreadsheet that integrates with your issues and pull requests on {% data variables.product.company_short %} to help you plan and track your work effectively. You can create and customize multiple views by filtering, sorting, grouping your issues and pull requests, adding custom fields to track metadata specific to your team, and visualize work with configurable charts. Rather than enforcing a specific methodology, a project provides flexible features you can customize to your team’s needs and processes. +プロジェクトは、{% data variables.product.company_short %}上のIssueやPull Requestと統合された適応性のあるスプレッドシートで、作業を効果的に計画し、追跡するのに役立ちます。 IssueやPull Requestをフィルタリングし、ソートし、グループ化して、チーム固有のメタデータを追跡するためのカスタムフィールドを追加し、設定可能なグラフで作業を可視化することによって、複数のビューを作成してカスタマイズできます。 プロジェクトは、特定の方法論を強制するのではなく、チームの要求やプロセスに合わせてカスタマイズ可能な重要な機能を提供します。 ### 最新の状態に保つ -Your projects are built from the issues and pull requests you add, creating direct references between your project and your work. Information is synced automatically to your project as you make changes, updating your views and charts. This integration works both ways, so that when you change information about a pull request or issue in your project, the pull request or issue reflects that information. For example, change an assignee in your project and that change is shown in your issue. You can take this integration even further, group your project by assignee, and make changes to issue assignment by dragging issues into the different groups. +プロジェクトは追加するIssueやPull Requestから構築され、プロジェクトと作業の間に直接の参照を作成します。 情報は変更があるたびにプロジェクトと自動的に同期され、ビューやグラフが更新されます。 この統合は双方向なので、Pull ReqeustやIssueに関する情報をプロジェクトから変更すると、そのPull RequestやIssueにはその情報が反映されます。 たとえばプロジェクトでアサインされた人を変更すると、その変更はIssueでも表示されます。 この統合をさらに推し進め、プロジェクトをアサインされた人でグループ化し、Issueを他のグループにドラッグすることによってIssueにアサインされた人を変更できます。 ### タスクへのメタデータの追加 -You can use custom fields to add metadata to your tasks and build a richer view of item attributes. You’re not limited to the built-in metadata (assignee, milestone, labels, etc.) that currently exists for issues and pull requests. For example, you can add the following metadata as custom fields: +カスタムフィールドを使って、タスクにメタデータを追加し、アイテムの属性のより豊かなビューを構築できます。 IssueやPull Requestに現在存在するビルトインのメタデータ（アサインされた人、マイルストーン、ラベルなど）に限定はされません。 たとえば、以下のメタデータをカスタムフィールドとして追加できます: -- A date field to track target ship dates. -- A number field to track the complexity of a task. -- A single select field to track whether a task is Low, Medium, or High priority. -- A text field to add a quick note. -- An iteration field to plan work week-by-week, including support for breaks. +- ターゲットの出荷日を追跡する日付フィールド。 +- タスクの複雑さを追跡する数値フィールド。 +- タスクの優先度が低、中、高なのかを追跡するための単一選択フィールド。 +- クイックノートを追加するためのテキストフィールド。 +- 休憩のサポートを含め、作業を週単位で計画するための繰り返しフィールド。 ### 様々な観点からプロジェクトを見る -Quickly answer your most pressing questions by tailoring your project view to give you the information you need. You can save these views, allowing you to quickly return to them as needed and make them available to your team. Views not only let you scope down the items listed but also offer two different layout options. +必要な情報が得られるようにプロジェクトのビューを調整して、最も差し迫った疑問に素早く答えてください。 それらのビューを保存して、必要なときにすぐに戻れるように、そしてチームでそれらを利用できるようにすることができます。 ビューはリストされたアイテムだけを対象とするだけでなく、2つの異なるレイアウトの選択肢も提供します。 プロジェクトは、高密度のテーブルレイアウトで表示できます。 @@ -46,4 +46,4 @@ Quickly answer your most pressing questions by tailoring your project view to gi ![プロジェクトのビュー](/assets/images/help/issues/project_view.png) -For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)." +詳しい情報については「[ビューのカスタマイズ](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)」を参照してください。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md index 73b2bb8ae6..69d65d93a6 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md @@ -1,6 +1,6 @@ --- -title: 'Best practices for {% data variables.product.prodname_projects_v2 %}' -intro: Learn tips for managing your projects. +title: '{% data variables.product.prodname_projects_v2 %}のベストプラクティス' +intro: プロジェクトを管理するためのヒントを学んでください。 allowTitleToDifferFromFilename: true miniTocMaxHeadingLevel: 3 versions: @@ -14,7 +14,7 @@ topics: - Project management --- -You can use {% data variables.product.prodname_projects_v2 %} to manage your work on {% data variables.product.company_short %}, where your issues and pull requests live. プロジェクトを効率的かつ効果的に管理するためのヒントを読んでください。 {% data variables.product.prodname_projects_v2 %} の詳細については、「[{% data variables.product.prodname_projects_v2 %} について](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)」を参照してください。 +{% data variables.product.prodname_projects_v2 %}を使って、IssueやPull Requestがある{% data variables.product.company_short %}上の作業を管理できます。 プロジェクトを効率的かつ効果的に管理するためのヒントを読んでください。 {% data variables.product.prodname_projects_v2 %} の詳細については、「[{% data variables.product.prodname_projects_v2 %} について](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)」を参照してください。 ## 大きなIssueを小さなIssueに分割する @@ -50,32 +50,32 @@ IssueとPull Requestには、コラボレータと容易にコミュニケーシ - カスタムの優先度フィールドでグループ化して、高優先度のアイテムの量をモニター - 最短の出荷ターゲット日でアイテムを見るために、カスタムの日付フィールドでソート -For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)." +詳しい情報については「[ビューのカスタマイズ](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)」を参照してください。 ## 信頼できる唯一の情報源を持つ 情報がずれてしまわないようにするために、信頼できる唯一の情報源を管理してください。 たとえば、ターゲットの出荷日は複数のフィールドに分散させず、一カ所で追跡してください。 そうすれば、ターゲットの出荷日が変更された場合、一カ所で日付を更新するだけでよくなります。 -{% data variables.product.prodname_projects_v2 %} automatically stay up to date with {% data variables.product.company_short %} data, such as assignees, milestones, and labels. これらのフィールドのいずれかがIssueあるいはPull Requestで変更されると、その変更は自動的にプロジェクトにも反映されます。 +{% data variables.product.prodname_projects_v2 %}は、アサインされた人、マイルストーン、ラベルといった{% data variables.product.company_short %}のデータと自動的に同期を保ちます。 これらのフィールドのいずれかがIssueあるいはPull Requestで変更されると、その変更は自動的にプロジェクトにも反映されます。 ## 自動化の利用 意味の無い作業に費やす時間を減らし、プロジェクト自体にかける時間を増やすために、タスクを自動化できます。 手動でやることを覚えておく必要が減れば、それだけプロジェクトは最新の状態に保たれるようになります。 -{% data variables.product.prodname_projects_v2 %} offers built-in workflows. たとえば、Issueがクローズされると自動的にステータスを「Done」に設定できます。 +{% data variables.product.prodname_projects_v2 %}はビルトインワークフローを提供します。 たとえば、Issueがクローズされると自動的にステータスを「Done」に設定できます。 加えて、{% data variables.product.prodname_actions %}とGraphQL APIでルーチンのプロジェクト管理タスクを自動化できます。 たとえば、レビュー待ちのPull Requestを追跡するために、Pull Requestをプロジェクトに追加し、そのステータスを"needs review"に設定するようなワークフローを作成できます。このプロセスは、Pull Requestが"ready for review"としてマークされたときに自動的にトリガーできます。 -- For an example workflow, see "[Automating {% data variables.product.prodname_projects_v2 %} using Actions](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)." -- For more information about the API, see "[Using the API to manage {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)." +- ワークフローの例については「[Actionsを使った{% data variables.product.prodname_projects_v2 %}の自動化](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)」を参照してください。 +- APIに関する詳しい情報については「[{% data variables.product.prodname_projects_v2 %}を管理するためのAPIの利用](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)」を参照してください。 - {% data variables.product.prodname_actions %}に関する詳しい情報については「[{% data variables.product.prodname_actions %}](/actions)」を参照してください。 ## 様々なフィールドタイプの利用 様々なフィールドタイプを活用して、要求を満たしてください。 -繰り返しフィールドを使って、作業をスケジュールしたり、タイムラインを作成したりしてください。 繰り返しをグループ化して、アイテムが繰り返し間でバランスしているかを見たり、あるいは繰り返しの1つに焦点を当てるためにフィルタリングできます。 繰り返しフィールドを使えば、過去の繰り返しで完了した作業を見ることもでき、それを速度の計画とチームの成果への反映に役立てられます。 繰り返しフィールドは、あなたとあなたのチームが繰り返しから離れる時間を取っている時を示す休憩もサポートします。 For more information, see "[About iteration fields](/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields)." +繰り返しフィールドを使って、作業をスケジュールしたり、タイムラインを作成したりしてください。 繰り返しをグループ化して、アイテムが繰り返し間でバランスしているかを見たり、あるいは繰り返しの1つに焦点を当てるためにフィルタリングできます。 繰り返しフィールドを使えば、過去の繰り返しで完了した作業を見ることもでき、それを速度の計画とチームの成果への反映に役立てられます。 繰り返しフィールドは、あなたとあなたのチームが繰り返しから離れる時間を取っている時を示す休憩もサポートします。 詳しい情報については「[繰り返しフィールドについて](/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields)」を参照してください。 単一の選択フィールドを利用して、事前設定された値のリストに基づき、タスクに関する情報を追跡してください。 たとえば、優先度やプロジェクトのフェーズを追跡してください。 値は事前設定されたリストから選択されるので、グループ化や特定の値のアイテムに集中するためのフィルタリングが容易です。 -For more information about the different field types, see "[Understanding field types](/issues/planning-and-tracking-with-projects/understanding-field-types)." +様々なフィールドタイプに関する詳しい情報については「[フィールドタイプを理解する](/issues/planning-and-tracking-with-projects/understanding-field-types)」を参照してください。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md index aed5d5a211..4070a3e055 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md @@ -1,6 +1,6 @@ --- -title: 'Learning about {% data variables.product.prodname_projects_v2 %}' -intro: 'Learn about {% data variables.product.prodname_projects_v2 %} and how to make the very best of this powerful tool.' +title: '{% data variables.product.prodname_projects_v2 %}について学ぶ' +intro: '{% data variables.product.prodname_projects_v2 %}について、そしてこの強力なツールを最大限に活用する方法を学んでください。' versions: feature: projects-v2 topics: diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md index 8ed93830a2..d4ca475134 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md @@ -1,6 +1,6 @@ --- -title: 'Quickstart for {% data variables.product.prodname_projects_v2 %}' -intro: 'Experience the speed, flexibility, and customization of {% data variables.product.prodname_projects_v2 %} by creating a project in this interactive guide.' +title: '{% data variables.product.prodname_projects_v2 %}のクイックスタート' +intro: 'このインタラクティブガイドでプロジェクトを作成して、{% data variables.product.prodname_projects_v2 %}のスピード、柔軟性、カスタマイズを体験してください。' allowTitleToDifferFromFilename: true miniTocMaxHeadingLevel: 3 versions: @@ -14,7 +14,7 @@ topics: ## はじめに -This guide demonstrates how to use {% data variables.product.prodname_projects_v2 %} to plan and track work. このガイドでは、新しいプロジェクトを作成し、タスクの優先度を追跡するためにカスタムフィールドを追加します。 また、コラボレータと優先度や進捗について伝えるための役に立つ、保存されるビューも作成します。 +このガイドは、作業を計画して追跡するための{% data variables.product.prodname_projects_v2 %}の使い方を紹介します。 このガイドでは、新しいプロジェクトを作成し、タスクの優先度を追跡するためにカスタムフィールドを追加します。 また、コラボレータと優先度や進捗について伝えるための役に立つ、保存されるビューも作成します。 ## 必要な環境 @@ -46,7 +46,7 @@ Organizationプロジェクトもしくはユーザプロジェクトを作成 上記のステップを何回か繰り返し、複数のIssueをプロジェクトに追加してください。 -For more information and other ways to add issues to your project, or about other items you can add to your project, see "[Adding items to your project](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)." +プロジェクトにIssueを追加する他の方法、あるいはプロジェクトに追加できる他のアイテムに関する情報については、「[プロジェクトへのアイテムの追加](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)」を参照してください。 ## プロジェクトへのドラフトIssueの追加 @@ -54,24 +54,24 @@ For more information and other ways to add issues to your project, or about othe {% data reusables.projects.add-draft-issue %} -## Adding an iteration field +## 繰り返しフィールドの追加 -Next, create an iteration field so you can plan and track your work over repeating blocks of time. Iterations can be configured to suit how you and your team works, with customizable lengths and the ability to insert breaks. +次に、繰り返しフィールドを作成して、繰り返される時間のブロックに対して作業を計画して追跡できるようにしましょう。 繰り返しは、長さがカスタマイズ可能で休憩を挟むことがき、あなたとあなたのチームの作業に合わせて設定できます。 {% data reusables.projects.new-field %} -1. Select **Iteration** ![Screenshot showing the iteration option](/assets/images/help/projects-v2/new-field-iteration.png) -3. それぞれの繰り返しの期間を変更するには、新しい数値を入力し、ドロップダウンを選択して**days（日）**もしくは**weeks（週）**をクリックしてください。 ![Screenshot showing the iteration duration](/assets/images/help/projects-v2/iteration-field-duration.png) -4. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save-and-create.png) +1. **Iteration（繰り返し）**を選択してください。 ![繰り返しのオプションを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-iteration.png) +3. それぞれの繰り返しの期間を変更するには、新しい数値を入力し、ドロップダウンを選択して**days（日）**もしくは**weeks（週）**をクリックしてください。 ![繰り返しの期間を表示しているスクリーンショット](/assets/images/help/projects-v2/iteration-field-duration.png) +4. [**Save**] をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-save-and-create.png) ## 優先度を追跡するためのフィールドの作成 -Now, create a custom field named `Priority` and containing the values: `High`, `Medium`, or `Low`. +さあ、`High`、`Medium`、`Low`のいずれかの値を含む`Priority`という名前のカスタムフィールドを作成してください。 {% data reusables.projects.new-field %} -1. Select **Single select** ![Screenshot showing the single select option](/assets/images/help/projects-v2/new-field-single-select.png) -1. Below "Options", type the first option, "High". ![Screenshot showing the single select option](/assets/images/help/projects-v2/priority-example.png) -1. To add additional fields, for "Medium" and "Low", click **Add option**. -1. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png) +1. **Single select（単一選択）**を選択してください。 ![単一選択オプションを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-single-select.png) +1. "Options（オプション）"の下で、最初の選択肢の"High"を入力してください。 ![単一選択オプションを表示しているスクリーンショット](/assets/images/help/projects-v2/priority-example.png) +1. "Medium"と"Low"のためのフィールドを追加するため、**Add option（選択肢の追加）**をクリックしてください。 +1. [**Save**] をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-save.png) プロジェクト中のすべてのIssueに優先度を指定してください。 @@ -82,8 +82,8 @@ Now, create a custom field named `Priority` and containing the values: `High`, ` 次に、高優先度のアイテムに集中しやすくするために、プロジェクト中のすべてのアイテムを優先度でグループ化します。 {% data reusables.projects.open-view-menu %} -1. Click {% octicon "rows" aria-label="the rows icon" %} **Group**. ![Screenshot showing the group menu item](/assets/images/help/projects-v2/group-menu-item.png) -1. Click **Priority**. ![Screenshot showing the group menu](/assets/images/help/projects-v2/group-menu.png) +1. {% octicon "rows" aria-label="the rows icon" %} **Group（グループ）**をクリックしてください。 ![グループメニューアイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/group-menu-item.png) +1. **Priority（優先度）**をクリックしてください。 ![グループメニューを表示しているスクリーンショット](/assets/images/help/projects-v2/group-menu.png) さあ、優先度を変更するために、Issueをグループ間で移動させてください。 @@ -117,7 +117,7 @@ Now, create a custom field named `Priority` and containing the values: `High`, ` 次に、ボードレイアウトに切り替えてください。 {% data reusables.projects.open-view-menu %} -1. Under "Layout", click **Board**. ![Screenshot showing layout option](/assets/images/help/projects-v2/table-or-board.png) +1. "Layout（レイアウト）"の下で、**Board（ボード）**をクリックしてください。 ![レイアウトオプションを表示しているスクリーンショット](/assets/images/help/projects-v2/table-or-board.png) ![優先度の例](/assets/images/help/projects/example_board.png) @@ -130,7 +130,7 @@ Now, create a custom field named `Priority` and containing the values: `High`, ` {% data reusables.projects.open-view-menu %} 1. {% octicon "pencil" aria-label="the pencil icon" %} **Rename view（ビューの名前の変更）**をクリックしてください。 ![名前の変更のメニューアイテムが表示されているスクリーンショット](/assets/images/help/projects-v2/rename-view.png) 1. ビューの新しい名前を入力してください。 -1. To save changes, press Return. +1. 変更を保存するためにReturnを押してください。 ![優先度の例](/assets/images/help/projects/project-view-switch.gif) @@ -138,12 +138,12 @@ Now, create a custom field named `Priority` and containing the values: `High`, ` 最後に、組み込みのワークフローを追加して、アイテムがプロジェクトに追加されたときにステータスが**Todo**に設定されるようにしてください。 -1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) -1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**. ![Screenshot showing the 'Workflows' menu item](/assets/images/help/projects-v2/workflows-menu-item.png) -1. **Default workflows（デフォルトのワークフロー）**の下で、**Item added to project（アイテムがプロジェクトに追加）**をクリックしてください。 ![Screenshot showing default workflows](/assets/images/help/projects-v2/default-workflows.png) -1. **When（時期）**の隣で、`issues`と`pull requests`がどちらも選択されていることを確認してください。 ![Screenshot showing the "when" configuration for a workflow](/assets/images/help/projects-v2/workflow-when.png) -1. **Set（設定）**の隣で、**Status:Todo**を選択してください。 ![Screenshot showing the "set" configuration for a workflow](/assets/images/help/projects-v2/workflow-set.png) -1. **Disabled（無効）**トグルをクリックして、ワークフローを有効化してください。 ![Screenshot showing the "enable" control for a workflow](/assets/images/help/projects-v2/workflow-enable.png) +1. 右上で{% octicon "kebab-horizontal" aria-label="The menu icon" %}をクリックしてメニューを開いてください。 ![メニューアイコンを表示しているスクリーンショット](/assets/images/help/projects-v2/open-menu.png) +1. メニューで{% octicon "workflow" aria-label="The workflow icon" %} **Workflows（ワークフロー）**をクリックしてください。 !['Workflows'メニューアイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/workflows-menu-item.png) +1. **Default workflows（デフォルトのワークフロー）**の下で、**Item added to project（アイテムがプロジェクトに追加）**をクリックしてください。 ![デフォルトのワークフローを表示しているスクリーンショット](/assets/images/help/projects-v2/default-workflows.png) +1. **When（時期）**の隣で、`issues`と`pull requests`がどちらも選択されていることを確認してください。 ![ワークフローの"when"設定を表示しているスクリーンショット](/assets/images/help/projects-v2/workflow-when.png) +1. **Set（設定）**の隣で、**Status:Todo**を選択してください。 ![ワークフローの"set"設定を表示しているスクリーンショット](/assets/images/help/projects-v2/workflow-set.png) +1. **Disabled（無効）**トグルをクリックして、ワークフローを有効化してください。 ![ワークフローの"enable"コントロールを表示しているスクリーンショット](/assets/images/help/projects-v2/workflow-enable.png) ## 参考リンク diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md index 7744c91356..efde8b15f8 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md @@ -1,7 +1,7 @@ --- -title: 'Adding items to your {% data variables.projects.project_v2 %}' -shortTitle: Adding items -intro: 'Learn how to add pull requests, issues, and draft issues to your projects individually or in bulk.' +title: '{% data variables.projects.project_v2 %}へのアイテムの追加' +shortTitle: アイテムの追加 +intro: Pull Request、Issue、ドラフトIssueをプロジェクトに個別あるいはまとめて追加する方法を学んでください。 miniTocMaxHeadingLevel: 4 versions: feature: projects-v2 @@ -15,13 +15,13 @@ allowTitleToDifferFromFilename: true {% note %} -**Note:** A project can contain a maximum of 1,200 items and 10,000 archived items. +**ノート:** プロジェクトには最大で1,200個のアイテム及び10,000個のアーカイブされたアイテムを含めることができます。 {% endnote %} -### Adding issues and pull requests to a project +### プロジェクトへのIssueやPull Requestの追加 -#### Pasting the URL of an issue or pull request +#### IssueあるいはPull RequestのURLの貼り付け {% data reusables.projects.add-item-via-paste %} @@ -29,13 +29,13 @@ allowTitleToDifferFromFilename: true {% data reusables.projects.add-item-bottom-row %} 2. #を入力してください。 -3. Pull RequestあるいはIssueがあるリポジトリを選択してください。 リポジトリ名の一部を入力して、選択肢を狭めることができます。 ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-item-select-repo.png) -4. IssueあるいはPull Requestを選択してください。 タイトルの一部を入力して、選択肢を狭めることができます。 ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-item-select-issue.png) +3. Pull RequestあるいはIssueがあるリポジトリを選択してください。 リポジトリ名の一部を入力して、選択肢を狭めることができます。 ![IssueのURLを貼り付けてプロジェクトに追加しているスクリーンショット](/assets/images/help/projects-v2/add-item-select-repo.png) +4. IssueあるいはPull Requestを選択してください。 タイトルの一部を入力して、選択肢を狭めることができます。 ![IssueのURLを貼り付けてプロジェクトに追加しているスクリーンショット](/assets/images/help/projects-v2/add-item-select-issue.png) -#### Bulk adding issues and pull requests +#### IssueやPull Requestの一括での追加 -1. In the bottom row of the project, click {% octicon "plus" aria-label="plus icon" %}. ![Screenshot showing + button at the bottom of the project](/assets/images/help/projects-v2/omnibar-add.png) -1. Click **Add item from repository**. ![Screenshot showing "add item from repository" menu item](/assets/images/help/projects-v2/add-bulk-menu-item.png) +1. プロジェクトの最下行で{% octicon "plus" aria-label="plus icon" %}をクリックしてください。 ![プロジェクトの下部に+ボタンが表示されているスクリーンショット](/assets/images/help/projects-v2/omnibar-add.png) +1. **Add item from repository（リポジトリからアイテムを追加）**をクリックしてください。 !["add item from repository" メニューアイテムが表示されているスクリーンショット](/assets/images/help/projects-v2/add-bulk-menu-item.png) {% data reusables.projects.bulk-add %} #### リポジトリから複数のIssueあるいはPull Requestを追加する @@ -44,25 +44,25 @@ allowTitleToDifferFromFilename: true {% data reusables.repositories.sidebar-issue-pr %} 1. それぞれのIssueのタイトルの左で、プロジェクトに追加したいIssueを選択してください。 ![IssueあるいはPull Requestを選択するためのチェックボックスが表示されているスクリーンショット](/assets/images/help/issues/select-issue-checkbox.png) 1. あるいは、ページ上のすべてのIssueあるいはPull Requestを選択するには、IssueあるいはPull Requestのリストの上部で、すべてを選択してください。 ![画面上のすべてを選択するためのチェックボックスが表示されているスクリーンショット](/assets/images/help/issues/select-all-checkbox.png) -1. Above the list of issues or pull requests, click **Projects**. ![Screenshot showing projects option](/assets/images/help/projects-v2/issue-index-project-menu.png) +1. IssueあるいはPull Requestのリストの上で**Projects（プロジェクト）**をクリックしてください。 ![プロジェクトのオプションが表示されているスクリーンショット](/assets/images/help/projects-v2/issue-index-project-menu.png) 1. 選択されたIssueあるいはPull Requestを追加したいプロジェクトをクリックしてください。 ![画面上のすべてを選択するためのチェックボックスが表示されているスクリーンショット](/assets/images/help/projects-v2/issue-index-select-project.png) #### IssueあるいはPull Requestの中からプロジェクトをアサインする 1. プロジェクトに追加したいIssueあるいはPull Requestにアクセスしてください。 -2. サイドバーで**Projects（プロジェクト）**をクリックしてください。 ![Screenshot showing "Projects" in the issue sidebar](/assets/images/help/projects-v2/issue-sidebar-projects.png) -3. Select the project that you want to add the issue or pull request to. ![Screenshot showing selecting a project from the issue sidebar](/assets/images/help/projects-v2/issue-sidebar-select-project.png) -4. Optionally, populate the custom fields. ![プロジェクトサイドバー](/assets/images/help/projects-v2/issue-edit-project-sidebar.png) +2. サイドバーで**Projects（プロジェクト）**をクリックしてください。 ![Issueサイドバーに"Projects"が表示されているスクリーンショット](/assets/images/help/projects-v2/issue-sidebar-projects.png) +3. IssueあるいはPull Requestを追加したいプロジェクトを選択してください。 ![Issueサイドバーからプロジェクトを選択しているところが表示されているスクリーンショット](/assets/images/help/projects-v2/issue-sidebar-select-project.png) +4. あるいは、カスタムフィールドに入力してください。 ![プロジェクトサイドバー](/assets/images/help/projects-v2/issue-edit-project-sidebar.png) -#### Using the command palette to add an issue or pull request +#### コマノン度パレットを使用してIssueあるいはPull Requestを追加する 1. {% data reusables.projects.open-command-palette %} -1. Start typing "Add items" and press Return. +1. "Add items"と入力し、Returnを押してください。 {% data reusables.projects.bulk-add %} ### ドラフトIssueの作成 -ドラフトIssueは、素早くアイデアを捕捉するのに役立ちます。 Unlike issues and pull requests that are referenced from your repositories, draft issues exist only in your project. +ドラフトIssueは、素早くアイデアを捕捉するのに役立ちます。 リポジトリから参照されるIssueやPull Requestとは異なり、ドラフトIssueはプロジェクトの中にだけ存在します。 {% data reusables.projects.add-draft-issue %} diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md index b7d40b5d3c..262b299aad 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md @@ -1,7 +1,7 @@ --- -title: 'Archiving items from your {% data variables.projects.project_v2 %}' -shortTitle: Archiving items -intro: 'You can archive items, keeping them available to restore, or permanently delete them.' +title: '{% data variables.projects.project_v2 %}からのアイテムのアーカイブ' +shortTitle: アイテムのアーカイブ +intro: アイテムをアーカイブし、復元できるようにしておくか、恒久的に削除できます。 miniTocMaxHeadingLevel: 2 versions: feature: projects-v2 @@ -11,29 +11,29 @@ topics: allowTitleToDifferFromFilename: true --- -## Archiving items +## アイテムのアーカイブ アイテムをアーカイブして、そのアイテムに関するコンテキストをプロジェクト中に保持しながら、アイテムをプロジェクトのビューから削除できます。 {% data reusables.projects.select-an-item %} {% data reusables.projects.open-item-menu %} -1. [**Archive**] をクリックします。 ![Screenshot showing archive option](/assets/images/help/projects-v2/archive-menu-item.png) -1. When prompted, confirm your choice by clicking **Archive**. ![Screenshot showing archive prompt](/assets/images/help/projects-v2/archive-item-prompt.png) +1. [**Archive**] をクリックします。 ![アーカイブのオプションが表示されているスクリーンショット](/assets/images/help/projects-v2/archive-menu-item.png) +1. プロンプトが表示されたら、**Archive（アーカイブ）**をクリックして選択を確認してください。 ![アーカイブのプロンプトが表示されているスクリーンショット](/assets/images/help/projects-v2/archive-item-prompt.png) ## アーカイブされたアイテムの復元 1. プロジェクトにアクセスします。 -1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) -1. In the menu, click {% octicon "archive" aria-label="The archive icon" %} **Archived items**. ![Screenshot showing the 'Archived items' menu item](/assets/images/help/projects-v2/archived-items-menu-item.png) -1. あるいは、表示されているアーカイブされたアイテムをフィルタリングするには、アイテムのリストの上にあるテキストボックスにフィルタを入力してください。 For more information about the available filters, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)." ![アーカイブされているアイテムをフィルタリングするためのフィールドが表示されているスクリーンショット](/assets/images/help/issues/filter-archived-items.png) -1. To the left of each item title, select the items you would like to restore. ![アーカイブされたアイテムの隣のチェックボックスが表示されているスクリーンショット](/assets/images/help/issues/select-archived-item.png) +1. 右上で{% octicon "kebab-horizontal" aria-label="The menu icon" %}をクリックしてメニューを開いてください。 ![メニューアイコンを表示しているスクリーンショット](/assets/images/help/projects-v2/open-menu.png) +1. メニューで{% octicon "archive" aria-label="The archive icon" %} **Archived items（アーカイブされたアイテム）**をクリックしてください。 ![Archived items'メニューアイテムが表示されているスクリーンショット](/assets/images/help/projects-v2/archived-items-menu-item.png) +1. あるいは、表示されているアーカイブされたアイテムをフィルタリングするには、アイテムのリストの上にあるテキストボックスにフィルタを入力してください。 利用可能なフィルタに関する詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 ![アーカイブされているアイテムをフィルタリングするためのフィールドが表示されているスクリーンショット](/assets/images/help/issues/filter-archived-items.png) +1. 各アイテムのタイトルの左で、復元したいアイテムを選択してください。 ![アーカイブされたアイテムの隣のチェックボックスが表示されているスクリーンショット](/assets/images/help/issues/select-archived-item.png) 1. 選択されたアイテムを復元するには、アイテムのリストの上部で**Restore（復元）**をクリックしてください。 !["復元"ボタンが表示されているスクリーンショット](/assets/images/help/issues/restore-archived-item-button.png) -## Deleting items +## アイテムの削除 アイテムを削除すれば、それをプロジェクトから完全に取り除くことができます。 {% data reusables.projects.select-an-item %} {% data reusables.projects.open-item-menu %} -1. Click **Delete from project**. ![Screenshot showing delete option](/assets/images/help/projects-v2/delete-menu-item.png) -1. When prompted, confirm your choice by clicking **Delete**. ![Screenshot showing delete prompt](/assets/images/help/projects-v2/delete-item-prompt.png) +1. **Delete from project（プロジェクトから削除）**をクリックしてください。 ![削除のオプションが表示されているスクリーンショット](/assets/images/help/projects-v2/delete-menu-item.png) +1. プロンプトが表示されたら、**Delete（削除）**をクリックして選択を確認してください。 ![削除のプロンプトが表示されているスクリーンショット](/assets/images/help/projects-v2/delete-item-prompt.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md index f7fe4c8931..8b313b1728 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md @@ -1,7 +1,7 @@ --- title: ドラフトIssueのIssueへの変換 -shortTitle: Converting draft issues -intro: Learn how to convert draft issues into issues. +shortTitle: ドラフトIssueの変換 +intro: ドラフトIssueをIssueに変換する方法を学んでください。 miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -10,18 +10,18 @@ topics: - Projects --- -## Converting draft issues in table layout +## テーブルレイアウトでのドラフトIssueの変換 -1. Click the {% octicon "triangle-down" aria-label="the item menu" %} on the draft issue that you want to convert. ![Screenshot showing item menu button](/assets/images/help/projects-v2/item-context-menu-button-table.png) -2. **Convert to issue（Issueに変換）**を選択してください。 ![Screenshot showing "Convert to issue" option](/assets/images/help/projects-v2/item-convert-to-issue.png) -3. Select the repository that you want to add the issue to. ![Screenshot showing repository selection](/assets/images/help/projects-v2/convert-to-issue-select-repo.png) +1. 変換したいドラフトIssueの{% octicon "triangle-down" aria-label="the item menu" %}をクリックしてください。 ![アイテムメニューボタンが表示されているスクリーンショット](/assets/images/help/projects-v2/item-context-menu-button-table.png) +2. **Convert to issue（Issueに変換）**を選択してください。 !["Convert to issue"オプションが表示されているスクリーンショット](/assets/images/help/projects-v2/item-convert-to-issue.png) +3. このIssueを追加したいリポジトリを選択してください。 ![リポジトリの選択が表示されているスクリーンショット](/assets/images/help/projects-v2/convert-to-issue-select-repo.png) -## Converting draft issues in board layout +## ボードレイアウトでのドラフトIssueの変換 -1. Click the {% octicon "kebab-horizontal" aria-label="the item menu" %} on the draft issue that you want to convert. ![Screenshot showing item menu button](/assets/images/help/projects-v2/item-context-menu-button-board.png) -2. **Convert to issue（Issueに変換）**を選択してください。 ![Screenshot showing "Convert to issue" option](/assets/images/help/projects-v2/item-convert-to-issue.png) -3. Select the repository that you want to add the issue to. ![Screenshot showing repository selection](/assets/images/help/projects-v2/convert-to-issue-select-repo.png) +1. 変換したいドラフトIssueの{% octicon "kebab-horizontal" aria-label="the item menu" %}をクリックしてください。 ![アイテムメニューボタンが表示されているスクリーンショット](/assets/images/help/projects-v2/item-context-menu-button-board.png) +2. **Convert to issue（Issueに変換）**を選択してください。 !["Convert to issue"オプションが表示されているスクリーンショット](/assets/images/help/projects-v2/item-convert-to-issue.png) +3. このIssueを追加したいリポジトリを選択してください。 ![リポジトリの選択が表示されているスクリーンショット](/assets/images/help/projects-v2/convert-to-issue-select-repo.png) ## 参考リンク -- "[Creating draft issues](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project#creating-draft-issues)" +- 「[ドラフトIssueの作成](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project#creating-draft-issues)」 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md index 0d43deeba0..ac61277e8a 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md @@ -1,7 +1,7 @@ --- -title: 'Managing items in your {% data variables.projects.project_v2 %}' -shortTitle: 'Managing items in your {% data variables.projects.project_v2 %}' -intro: 'Learn how to add and manage issues, pull requests, and draft issues.' +title: '{% data variables.projects.project_v2 %}内のアイテムの管理' +shortTitle: '{% data variables.projects.project_v2 %}内のアイテムの管理' +intro: Issue、Pull Request、ドラフトIssueの追加と管理の方法を学んでください。 versions: feature: projects-v2 topics: diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md index 03f355e94c..8b5e1ccb52 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md @@ -1,7 +1,7 @@ --- -title: 'Adding your {% data variables.projects.project_v2 %} to a repository' -shortTitle: 'Adding a {% data variables.projects.project_v2 %} to a repo' -intro: 'You can add your {% data variables.projects.project_v2 %} to a repository to make it accessible from that repository.' +title: '{% data variables.projects.project_v2 %}のリポジトリへの追加' +shortTitle: '{% data variables.projects.project_v2 %}のリポジトリへの追加' +intro: '{% data variables.projects.project_v2 %}をリポジトリへ追加して、リポジトリからアクセスできるようにすることができます。' miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -13,10 +13,10 @@ allowTitleToDifferFromFilename: true リポジトリ中で、関連するプロジェクトをリストできます。 リストできるのは、リポジトリを所有している同じユーザもしくはOrganizationが所有しているプロジェクトだけです。 -リポジトリのメンバーがリストされているプロジェクトを見るためには、そのプロジェクトを見ることができなければなりません。 For more information, see "[Managing visibility of your {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)" and "[Managing access to your {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)." +リポジトリのメンバーがリストされているプロジェクトを見るためには、そのプロジェクトを見ることができなければなりません。 詳しい情報については「[{% data variables.projects.projects_v2 %}の可視性の管理](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)」及び「[{% data variables.projects.projects_v2 %}へのアクセスの管理](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)」を参照してください。 1. {% data variables.product.prodname_dotcom %}で、リポジトリのメインページにアクセスしてください。 -1. {% octicon "table" aria-label="the project icon" %} **Projects（プロジェクト）**をクリックしてください。 ![Screenshot showing projects tab in a repository](/assets/images/help/projects-v2/repo-tab.png) -1. **Add project（プロジェクトの追加）**をクリックしてください。 ![Screenshot showing "Add project" button](/assets/images/help/projects-v2/add-to-repo-button.png) -1. In the search bar that appears, search for projects that are owned by the same user or organization that owns the repository. ![Screenshot showing searching for a project](/assets/images/help/projects-v2/add-to-repo-search.png) -1. Click on a project to list it in your repository. ![Screenshot showing "Add project" button](/assets/images/help/projects-v2/add-to-repo.png) +1. {% octicon "table" aria-label="the project icon" %} **Projects（プロジェクト）**をクリックしてください。 ![リポジトリのプロジェクトタブが表示されているスクリーンショット](/assets/images/help/projects-v2/repo-tab.png) +1. **Add project（プロジェクトの追加）**をクリックしてください。 !["Add project"ボタンが表示されているスクリーンショット](/assets/images/help/projects-v2/add-to-repo-button.png) +1. 表示される検索バーで、リポジトリを所有しているのと同じユーザあるいはOrganizationが所有しているプロジェクトを検索してください。 ![プロジェクトを検索しているところを表示しているスクリーンショット](/assets/images/help/projects-v2/add-to-repo-search.png) +1. リポジトリでリストされているプロジェクトをクリックしてください。 !["Add project"ボタンが表示されているスクリーンショット](/assets/images/help/projects-v2/add-to-repo.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md index 457ba55c97..59ee204fb5 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md @@ -1,7 +1,7 @@ --- -title: 'Closing and deleting your {% data variables.projects.projects_v2 %}' -shortTitle: 'Closing and deleting {% data variables.projects.projects_v2 %}' -intro: 'Learn about closing, re-opening, and permanently deleting a {% data variables.projects.project_v2 %}.' +title: '{% data variables.projects.projects_v2 %}のクローズと削除' +shortTitle: '{% data variables.projects.projects_v2 %}のクローズと削除' +intro: '{% data variables.projects.project_v2 %}のクローズ、再オープン、完全な削除について学んでください。' miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md index ad6852040f..3c65ece66b 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md @@ -1,6 +1,6 @@ --- -title: 'Managing your {% data variables.projects.project_v2 %}' -intro: Learn how to manage your projects and control visibility and access. +title: '{% data variables.projects.project_v2 %}の管理' +intro: プロジェクトの管理と、可視性及びアクセスの制御の方法を学んでください。 versions: feature: projects-v2 topics: diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md index 0a3b38f596..cd1bd40c98 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md @@ -1,7 +1,7 @@ --- -title: 'Managing access to your {% data variables.projects.projects_v2 %}' -shortTitle: 'Managing {% data variables.projects.project_v2 %} access' -intro: 'Learn how to manage team and individual access to your {% data variables.projects.project_v2 %}.' +title: '{% data variables.projects.projects_v2 %}へのアクセスの管理' +shortTitle: '{% data variables.projects.project_v2 %}のアクセスの管理' +intro: '{% data variables.projects.project_v2 %}のTeam及び個人のアクセス管理の方法を学んでください。' miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -29,8 +29,8 @@ Organizationレベルのプロジェクトの管理者は、Organization全体 デフォルトの基本ロールは`write`であり、これはOrganization内の誰もがプロジェクトを見て編集できるということです。 この基本ロールを変更すれば、Organizationの全員に対するプロジェクトのアクセスを変更できます。 基本ロールへの変更は、Organizationのオーナーではなく、個別にアクセス権を付与されていないOrganizaitonのメンバーにだけ影響します。 {% data reusables.projects.project-settings %} -1. **Manage access（アクセス管理）**をクリックしてください。 ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png) -2. **Base role（基本ロール）**の下で、デフォルトロールを選択してください。 ![Screenshot showing the base role menu](/assets/images/help/projects-v2/base-role.png) +1. **Manage access（アクセス管理）**をクリックしてください。 !["Manage access"アイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/manage-access.png) +2. **Base role（基本ロール）**の下で、デフォルトロールを選択してください。 ![ベースロールメニューを表示しているスクリーンショット](/assets/images/help/projects-v2/base-role.png) - **No access（アクセス無し）**: Organizationのオーナーと、個別にアクセス権を付与されたユーザだけがプロジェクトを見ることができます。 Organizationのオーナーは、プロジェクトの管理者でもあります。 - **Read（読み取り）**: Organizationの全員がプロジェクトを見ることができます。 Organizationのオーナーは、プロジェクトの管理者でもあります。 - **Write（書き込み）**: Organizationの全員がプロジェクトを見て編集できます。 Organizationのオーナーは、プロジェクトの管理者でもあります。 @@ -43,24 +43,24 @@ Organizationレベルのプロジェクトには、Team、外部のコラボレ 個人ユーザが既にOrganizationのメンバーになっているか、Organizationの少なくとも1つのリポジトリで外部のコラボレータになっている場合にのみ、Organizationレベルのプロジェクトに共同作業をするように招待できます。 {% data reusables.projects.project-settings %} -1. **Manage access（アクセス管理）**をクリックしてください。 ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png) -2. **Invite collaborators（コラボレータの招待）**の下で、招待したいTeamもしくは個人ユーザを検索してください。 ![Screenshot showing searching for a collaborator](/assets/images/help/projects-v2/access-search.png) -3. Select the role for the collaborator. ![Screenshot showing selecting a role](/assets/images/help/projects-v2/access-role.png) +1. **Manage access（アクセス管理）**をクリックしてください。 !["Manage access"アイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/manage-access.png) +2. **Invite collaborators（コラボレータの招待）**の下で、招待したいTeamもしくは個人ユーザを検索してください。 ![コラボレータの検索を表示しているスクリーンショット](/assets/images/help/projects-v2/access-search.png) +3. コラボレータのロールを選択してください。 ![ロールの選択を表示しているスクリーンショット](/assets/images/help/projects-v2/access-role.png) - **Read（読み取り）**: Teamあるいは個人はプロジェクトを見ることができます。 - **Write（書き込み）**: Teamあるいは個人はプロジェクトを編集できます。 - **Admin（管理）**: Teamあるいは個人はプロジェクトを見て編集でき、新しいコラボレータを追加できます。 -4. **Invite（招待）**をクリックしてください。 ![Screenshot showing the invite button](/assets/images/help/projects-v2/access-invite.png) +4. **Invite（招待）**をクリックしてください。 ![招待ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/access-invite.png) ### プロジェクトの既存のコラボレータのアクセス管理 {% data reusables.projects.project-settings %} -1. **Manage access（アクセス管理）**をクリックしてください。 ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png) +1. **Manage access（アクセス管理）**をクリックしてください。 !["Manage access"アイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/manage-access.png) 1. **Manage access（アクセス管理）**の下で、権限を変更したいコラボレータを見つけてください。 - **Type（タイプ）**及び**Role（ロール）**ドロップダウンメニューを使って、アクセスリストをフィルタリングできます。 ![Screenshot showing a collaborator](/assets/images/help/projects-v2/access-find-member.png) + **Type（タイプ）**及び**Role（ロール）**ドロップダウンメニューを使って、アクセスリストをフィルタリングできます。 ![コラボレータを表示しているスクリーンショット](/assets/images/help/projects-v2/access-find-member.png) -1. Edit the role for the collaborator(s). ![Screenshot showing changing a collaborator's role](/assets/images/help/projects-v2/access-change-role.png) -1. Optionally, click **Remove** to remove the collaborator(s). ![Screenshot showing removing a collaborator](/assets/images/help/projects-v2/access-remove-member.png) +1. コラボレータのロールを編集してください。 ![コラボレータのロールの変更を表示しているスクリーンショット](/assets/images/help/projects-v2/access-change-role.png) +1. あるいは、**Remove（削除）** をクリックしてコラボレータを削除してください。 ![コラボレータの削除を表示しているスクリーンショット](/assets/images/help/projects-v2/access-remove-member.png) ## ユーザレベルプロジェクトのアクセス管理 @@ -73,21 +73,21 @@ Organizationレベルのプロジェクトには、Team、外部のコラボレ {% endnote %} {% data reusables.projects.project-settings %} -1. **Manage access（アクセス管理）**をクリックしてください。 ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png) -2. **Invite collaborators（コラボレータの招待）**の下で、招待したいユーザを検索してください。 ![Screenshot showing searching for a collaborator](/assets/images/help/projects-v2/access-search.png) -3. Select the role for the collaborator. ![Screenshot showing selecting a role](/assets/images/help/projects-v2/access-role.png) +1. **Manage access（アクセス管理）**をクリックしてください。 !["Manage access"アイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/manage-access.png) +2. **Invite collaborators（コラボレータの招待）**の下で、招待したいユーザを検索してください。 ![コラボレータの検索を表示しているスクリーンショット](/assets/images/help/projects-v2/access-search.png) +3. コラボレータのロールを選択してください。 ![ロールの選択を表示しているスクリーンショット](/assets/images/help/projects-v2/access-role.png) - **Read（読み取り）**: ユーザはプロジェクトを見ることができます。 - **Write（書き込み）**: ユーザはプロジェクトを見て編集できます。 - **Admin（管理）**: ユーザはプロジェクトを見て編集でき、新しいコラボレータを追加できます。 -4. **Invite（招待）**をクリックしてください。 ![Screenshot showing the invite button](/assets/images/help/projects-v2/access-invite.png) +4. **Invite（招待）**をクリックしてください。 ![招待ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/access-invite.png) ### プロジェクトの既存のコラボレータのアクセス管理 {% data reusables.projects.project-settings %} -1. **Manage access（アクセス管理）**をクリックしてください。 ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png) +1. **Manage access（アクセス管理）**をクリックしてください。 !["Manage access"アイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/manage-access.png) 1. **Manage access（アクセス管理）**の下で、権限を変更したいコラボレータを見つけてください。 - **Type（タイプ）**及び**Role（ロール）**ドロップダウンメニューを使って、アクセスリストをフィルタリングできます。 ![Screenshot showing a collaborator](/assets/images/help/projects-v2/access-find-member.png) + **Type（タイプ）**及び**Role（ロール）**ドロップダウンメニューを使って、アクセスリストをフィルタリングできます。 ![コラボレータを表示しているスクリーンショット](/assets/images/help/projects-v2/access-find-member.png) -1. Edit the role for the collaborator(s). ![Screenshot showing changing a collaborator's role](/assets/images/help/projects-v2/access-change-role.png) -1. Optionally, click **Remove** to remove the collaborator(s). ![Screenshot showing removing a collaborator](/assets/images/help/projects-v2/access-remove-member.png) +1. コラボレータのロールを編集してください。 ![コラボレータのロールの変更を表示しているスクリーンショット](/assets/images/help/projects-v2/access-change-role.png) +1. あるいは、**Remove（削除）** をクリックしてコラボレータを削除してください。 ![コラボレータの削除を表示しているスクリーンショット](/assets/images/help/projects-v2/access-remove-member.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md index d2150a6fc7..ae755d0bbc 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md @@ -1,7 +1,7 @@ --- -title: 'Managing visibility of your {% data variables.projects.projects_v2 %}' -shortTitle: 'Managing {% data variables.projects.project_v2 %} visibility' -intro: 'Learn about setting your {% data variables.projects.project_v2 %} to private or public visibility.' +title: '{% data variables.projects.projects_v2 %}の可視性の管理' +shortTitle: '{% data variables.projects.project_v2 %}の可視性の管理' +intro: '{% data variables.projects.project_v2 %}の可視性のプライベートもしくはパブリックへの設定について学んでください。' miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -16,25 +16,25 @@ permissions: Organization owners can manage the visibility of project boards in ## プロジェクトの可視性について -Projects can be public or private. パブリックプロジェクトでは、インターネット上の誰もがプロジェクトを見ることができます。 プライベートプロジェクトでは、最低でも読み取りアクセスを付与されたユーザだけがプロジェクトを見ることができます。 +プロジェクトはパブリックあるいはプライベートにできます。 パブリックプロジェクトでは、インターネット上の誰もがプロジェクトを見ることができます。 プライベートプロジェクトでは、最低でも読み取りアクセスを付与されたユーザだけがプロジェクトを見ることができます。 影響を受けるのはプロジェクトの可視性のみです。プロジェクト上のアイテムを見るには、アイテムが属する得リポジトリに対する必要な権限を持っていなければなりません。 プロジェクトにプライベートリポジトリのアイテムが含まれているなら、そのリポジトリのコラボレータではないユーザは、そのリポジトリのアイテムを見ることはできません。 ![非表示のアイテムを持つプロジェクト](/assets/images/help/projects/hidden-items.png) -Project admins and organization owners can control project visibility. Organization owners can restrict the ability to change project visibility to just organization owners. +プロジェクトの管理者とOrganizationのオーナーは、プロジェクトの可視性を制御できます。 Organizationのオーナーは、プロジェクトの可視性を変更できるのをOrganizationのオーナーだけに制限できます。 -In public and private projects, insights are only visible to users with write permissions for the project. +パブリック及びプライベートのプロジェクトでは、インサイトはプロジェクトの書き込み権限を持っているユーザだけが見ることができます。 Organizationが所有するプライベートのプロジェクトでは、プロジェクトを現在更新しているユーザのアバターがプロジェクトのUIに表示されます。 -プロジェクトの管理者は、プロジェクトに対する書き込み及び管理アクセスの管理と、個々のユーザの読み取りアクセスの制御もできます。 For more information, see "[Managing access to your projects](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)." +プロジェクトの管理者は、プロジェクトに対する書き込み及び管理アクセスの管理と、個々のユーザの読み取りアクセスの制御もできます。 詳しい情報については「[プロジェクトへのアクセスの管理](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)」を参照してください。 ## プロジェクトの可視性の変更 {% data reusables.projects.project-settings %} -1. Next to **Visibility** in the "Danger zone", select **Private** or **Public**. ![Screenshot showing the visibility controls](/assets/images/help/projects-v2/visibility.png) +1. "Danger zone（危険区域）"の**Visibility（可視性）**の隣で、**Private（プライベート）**もしくは**Public（パブリック）**を選択してください。 ![可視性のコントロールを表示しているスクリーンショット](/assets/images/help/projects-v2/visibility.png) ## 参考リンク -- [Allowing project visibility changes in your organization](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization) +- [Organizationでのプロジェクトの可視性の変更の許可](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md index 21a0bc288a..47f43f9d19 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md @@ -1,7 +1,7 @@ --- -title: About date fields -shortTitle: About date fields -intro: You can create custom date fields that can be set by typing a date or using a calendar. +title: 日付フィールドについて +shortTitle: 日付フィールドについて +intro: 日付を入力するか、カレンダーを使って設定できるカスタムの日付フィールドを作成できます。 miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -10,12 +10,12 @@ topics: - Projects --- -You can filter for date values using the `YYYY-MM-DD` format, for example: `date:2022-07-01`. You can also use operators, such as `>`, `>=`, `<`, `<=`, and `..`. For example, `date:>2022-07-01` and `date:2022-07-01..2022-07-31`. You can also provide `@today` to represent the current day in your filter. 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 +日付の値を、たとえば`date:2022-07-01`のような`YYYY-MM-DD`という形式を使ってフィルタリングできます。 `>`、`>=`、`<`、`<=`、`..`といった演算子を使うこともできます。 たとえば`date:>2022-07-01`や`date:2022-07-01..2022-07-31`のようにです。 `@today`としてフィルタ中で今日の日付を示すこともできます。 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 -## Adding a date field +## 日付フィールドの追加 {% data reusables.projects.new-field %} -1. Select **Date** ![Screenshot showing the date option](/assets/images/help/projects-v2/new-field-date.png) -1. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png) +1. **Date（日付）**を選択してください。 ![日付のオプションを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-date.png) +1. [**Save**] をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-save.png) -Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field." +または、{% data variables.projects.command-palette-shortcut %}を押してプロジェクトのコマンドパレットをオープンし、"Create new field"と入力していってください。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md index 3fa989b258..f30706c2bf 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md @@ -1,6 +1,6 @@ --- -title: About iteration fields -shortTitle: About iteration fields +title: 繰り返しフィールドについて +shortTitle: 繰り返しフィールドについて intro: 今後の作業を計画し、アイテムをグループ化するために、繰り返しを作成できます。 miniTocMaxHeadingLevel: 3 versions: @@ -14,47 +14,47 @@ topics: 繰り返しフィールドを作成して、アイテムを特定の繰り返し時間ブロックに関連づけることができます。 繰り返しは任意の長さに設定でき、休憩を含められ、名前と日付の範囲を変更するために個別に編集できます。 プロジェクトでは、繰り返しでグループ化を行い、今後の作業のバランスを視覚化し、フィルタを使って繰り返しの1つに焦点を当て、繰り返しで並べ替えできます。 -You can filter for iterations by specifying the iteration name or `@current` for the current iteration, `@previous` for the previous iteration, or `@next` for the next iteration. You can also use operators such as `>`, `>=`, `<`, `<=`, and `..`. For example, `iteration:>"Iteration 4"` and `iteration:<@current`. 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 +繰り返しの名前もしくは現在の繰り返しとして`@current`、前の繰り返しとして`@previous`、次の繰り返しとして`@next`を指定して、繰り返しをフィルタリングできます。 `>`、`>=`、`<`、`<=`、`..`といった演算子を使うこともできます。 たとえば`iteration:>"Iteration 4"`や`iteration:<@current`とできます。 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 最初に繰り返しフィールドを作成すると、3回の繰り返しが自動的に作成されます。 プロジェクトの設定ページから、繰り返しを追加したり、他の変更をしたりできます。 ![繰り返しフィールドの設定を表示しているスクリーンショット](/assets/images/help/issues/iterations-example.png) -## Adding an iteration field +## 繰り返しフィールドの追加 {% data reusables.projects.new-field %} -1. Select **Iteration** ![Screenshot showing the iteration option](/assets/images/help/projects-v2/new-field-iteration.png) -2. Optionally, if you don't want the iteration to start today, select the calendar dropdown next to "Starts on" and choose a new start date. ![Screenshot showing the iteration start date](/assets/images/help/projects-v2/iteration-field-starts.png) -3. それぞれの繰り返しの期間を変更するには、新しい数値を入力し、ドロップダウンを選択して**days（日）**もしくは**weeks（週）**をクリックしてください。 ![Screenshot showing the iteration duration](/assets/images/help/projects-v2/iteration-field-duration.png) -4. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save-and-create.png) +1. **Iteration（繰り返し）**を選択してください。 ![繰り返しのオプションを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-iteration.png) +2. あるいは、繰り返しを今日始めたくない場合は、"Starts on（開始）"の隣のカレンダードロップダウンを選択し、新しい開始日を選択してください。 ![繰り返しの開始日を表示しているスクリーンショット](/assets/images/help/projects-v2/iteration-field-starts.png) +3. それぞれの繰り返しの期間を変更するには、新しい数値を入力し、ドロップダウンを選択して**days（日）**もしくは**weeks（週）**をクリックしてください。 ![繰り返しの期間を表示しているスクリーンショット](/assets/images/help/projects-v2/iteration-field-duration.png) +4. [**Save**] をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-save-and-create.png) -Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field." +または、{% data variables.projects.command-palette-shortcut %}を押してプロジェクトのコマンドパレットをオープンし、"Create new field"と入力していってください。 ## 新しい繰り返しの追加 {% data reusables.projects.project-settings %} -1. Click the name of the iteration field you want to adjust. ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-iteration-field.png) -1. 同じ期間の新しい繰り返しを追加したいなら、**Add iteration（繰り返しの追加）**をクリックしてください。 ![Screenshot the "add iteration" button](/assets/images/help/projects-v2/add-iteration.png) -1. Optionally, to customize the duration of the new iteration and when it will start, click {% octicon "triangle-down" aria-label="The triangle icon" %} **More options**, select a starting date and duration, and click **Add**. ![Screenshot the add iteration options form](/assets/images/help/projects-v2/add-iteration-options.png) -1. [**Save changes**] をクリックします。 ![Screenshot the save button](/assets/images/help/projects-v2/iteration-save.png) +1. 調整したい繰り返しフィールドの名前をクリックしてください。 ![繰り返しフィールドを表示しているスクリーンショット](/assets/images/help/projects-v2/select-iteration-field.png) +1. 同じ期間の新しい繰り返しを追加したいなら、**Add iteration（繰り返しの追加）**をクリックしてください。 !["add iteration"ボタンのスクリーンショット](/assets/images/help/projects-v2/add-iteration.png) +1. あるいは、新しい繰り返しの期間と開始時点をカスタマイズしたいなら、{% octicon "triangle-down" aria-label="The triangle icon" %} **More options（追加のオプション）**をクリックし、開始日と期間を選択し、**Add（追加）**をクリックしてください。 ![繰り返しの追加オプションフォームのスクリーンショット](/assets/images/help/projects-v2/add-iteration-options.png) +1. [**Save changes**] をクリックします。 ![保存ボタンのスクリーンショット](/assets/images/help/projects-v2/iteration-save.png) ## 繰り返しの編集 繰り返しは、プロジェクトの設定で編集できます。 繰り返しフィールドの設定には、フィールドの表ヘッダ内の{% octicon "triangle-down" aria-label="The triangle icon" %}をクリックし、**Edit values（値の編集）**をクリックしてもアクセスできます。 {% data reusables.projects.project-settings %} -1. Click the name of the iteration field you want to adjust. ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-iteration-field.png) -1. To change the name of an iteration, click on the name and start typing. ![Screenshot an title field to rename an iteration](/assets/images/help/projects-v2/iteration-rename.png) -1. 繰り返しの日付や期間を変更するには、日付をクリックしてカレンダーを開いてください。 開始日をクリックし、続いて終了日をクリックし、そして**Apply（適用）**をクリックしてください。 ![Screenshot showing iteration dates](/assets/images/help/projects-v2/iteration-date.png) -1. Optionally, to delete an iteration, click {% octicon "trash" aria-label="The trash icon" %}. ![Screenshot the delete button](/assets/images/help/projects-v2/iteration-delete.png) -2. [**Save changes**] をクリックします。 ![Screenshot the save button](/assets/images/help/projects-v2/iteration-save.png) +1. 調整したい繰り返しフィールドの名前をクリックしてください。 ![繰り返しフィールドを表示しているスクリーンショット](/assets/images/help/projects-v2/select-iteration-field.png) +1. 繰り返しの名前を変更するには、名前をクリックして入力していってください。 ![繰り返しの名前を変更するタイトルフィールドのスクリーンショット](/assets/images/help/projects-v2/iteration-rename.png) +1. 繰り返しの日付や期間を変更するには、日付をクリックしてカレンダーを開いてください。 開始日をクリックし、続いて終了日をクリックし、そして**Apply（適用）**をクリックしてください。 ![繰り返しの日付を表示しているスクリーンショット](/assets/images/help/projects-v2/iteration-date.png) +1. あるいは、繰り返しを削除したい場合は{% octicon "trash" aria-label="The trash icon" %}をクリックしてください。 ![削除ボタンのスクリーンショット](/assets/images/help/projects-v2/iteration-delete.png) +2. [**Save changes**] をクリックします。 ![保存ボタンのスクリーンショット](/assets/images/help/projects-v2/iteration-save.png) ## 休憩の挿入 繰り返しには、スケジュールされた作業から離れることを知らせるために休憩を挿入できます。 新しい休憩期間のデフォルトは、直近に作成された繰り返しの長さです。 {% data reusables.projects.project-settings %} -1. Click the name of the iteration field you want to adjust. ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-iteration-field.png) +1. 調整したい繰り返しフィールドの名前をクリックしてください。 ![繰り返しフィールドを表示しているスクリーンショット](/assets/images/help/projects-v2/select-iteration-field.png) 2. 繰り返しの上の分割線上の右で**Insert break（休憩の挿入）**をクリックしてください。 !["休憩の挿入"ボタンの場所を表示しているスクリーンショット](/assets/images/help/issues/iteration-insert-break.png) 3. あるいは、休憩の期間を変更するには、日付をクリックしてカレンダーを開いてください。 開始日をクリックし、続いて終了日をクリックし、そして**Apply（適用）**をクリックしてください。 -4. [**Save changes**] をクリックします。 ![Screenshot the save button](/assets/images/help/projects-v2/iteration-save.png) +4. [**Save changes**] をクリックします。 ![保存ボタンのスクリーンショット](/assets/images/help/projects-v2/iteration-save.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md index fdb76a38e7..393209f0e0 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md @@ -1,7 +1,7 @@ --- -title: About single select fields -shortTitle: About single select fields -intro: You can create single select fields with defined options that can be selected from a dropdown menu. +title: 単一選択フィールドについて +shortTitle: 単一選択フィールドについて +intro: ドロップダウンメニューから選択できる定義済みの選択肢で単一選択フィールドを作成できます。 miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -10,24 +10,24 @@ topics: - Projects --- -You can filter by your single select fields by specifying the option, for example: `fieldname:option`. You can filter for multiple values by providing a comma-separated list of options, for example: `fieldname:option,option`. 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 +単一選択フィールドは、たとえば`fieldname:option`のようにオプションを指定してフィルタリングできます。 たとえば`fieldname:option,option`というように、カンマ区切りのリストのオプションを渡すことで、複数の値に対してフィルタリングできます。 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 -Single select fields can contain up to 50 options. +単一選択フィールドは、最大で50個の選択肢を含むことができます。 -## Adding a single select field +## 単一選択フィールドの追加 {% data reusables.projects.new-field %} -1. Select **Single select** ![Screenshot showing the single select option](/assets/images/help/projects-v2/new-field-single-select.png) -1. Below "Options", type the first option. ![Screenshot showing the single select option](/assets/images/help/projects-v2/single-select-create-with-options.png) - - To add additional options, click **Add option**. -1. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png) +1. **Single select（単一選択）**を選択してください。 ![単一選択の選択肢を表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-single-select.png) +1. "Options（選択肢）"の下で、最初の選択肢を入力してください。 ![単一選択の選択肢を表示しているスクリーンショット](/assets/images/help/projects-v2/single-select-create-with-options.png) + - 選択肢を追加するには**Add option（選択肢の追加）**をクリックしてください。 +1. [**Save**] をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-save.png) -Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field." +または、{% data variables.projects.command-palette-shortcut %}を押してプロジェクトのコマンドパレットをオープンし、"Create new field"と入力していってください。 -## Editing a single select field +## 単一選択フィールドの編集 {% data reusables.projects.project-settings %} -1. Click the name of the single select field you want to adjust. ![Screenshot showing an single select field](/assets/images/help/projects-v2/select-single-select.png) -1. Edit existing options or click **Add option**. ![Screenshot showing single select options](/assets/images/help/projects-v2/single-select-edit-options.png) -1. Optionally, to delete an option, click {% octicon "x" aria-label="The x icon" %}. ![Screenshot showing delete button](/assets/images/help/projects-v2/single-select-delete.png) -1. Click **Save options**. ![Screenshot showing save button](/assets/images/help/projects-v2/save-options.png) +1. 調整したい単一選択フィールドの名前をクリックしてください。 ![単一選択フィールドを表示しているスクリーンショット](/assets/images/help/projects-v2/select-single-select.png) +1. 既存の選択肢を編集するか、**Add option（選択肢の追加）**をクリックしてください。 ![単一選択の選択肢を表示しているスクリーンショット](/assets/images/help/projects-v2/single-select-edit-options.png) +1. あるいは、選択肢を削除したい場合は{% octicon "x" aria-label="The x icon" %}をクリックしてください。 ![削除ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/single-select-delete.png) +1. **Save options（選択肢の保存）**をクリックしてください。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/save-options.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md index e07cb71d3f..4abb2def2b 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md @@ -1,7 +1,7 @@ --- -title: About text and number fields -shortTitle: About text and number fields -intro: You can add custom text and number fields to your project. +title: テキスト及び数値フィールドについて +shortTitle: テキスト及び数値フィールドについて +intro: プロジェクトに、カスタムのテキスト及び数値フィールドを追加できます。 miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -10,24 +10,24 @@ topics: - Projects --- -You can use text fields to include notes or any other freeform text in your project. +テキストフィールドを使ってノートやその他の自由形式のテキストをプロジェクトに含めることができます。 -Text fields can be used in filters, for example: `field:"exact text"`. Text fields and item titles will also be used if you filter for text without specifying a field. +テキストフィールドは、たとえば`field:"exact text"`というようにフィルタで使うことができます。 テキストフィールドとアイテムのタイトルは、フィールドを指定せずにテキストに対してフィルタを掛けた場合にも使われます。 -Number fields can also be used in filters. You can use `>`, `>=`, `<`, `<=`, and `..` range queries to filter by a number field. For example: `field:5..15` or `field:>=20`. 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 +数値フィールドもフィルタで利用できます。 `>`、`>=`、`<`、`<=`、`..`といった範囲修飾子を数値フィールドでのフィルタリングのために利用できます。 たとえば`field:5..15`あるいは`field:>=20`といったようにできます。 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 -## Adding a text field +## テキストフィールドの追加 {% data reusables.projects.new-field %} -1. Select **Text** ![Screenshot showing the text option](/assets/images/help/projects-v2/new-field-text.png) -1. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png) +1. **Text（テキスト）**を選択してください。 ![テキストのオプションを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-text.png) +1. **Save（保存）**をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-save.png) -Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field." +または、{% data variables.projects.command-palette-shortcut %}を押してプロジェクトのコマンドパレットをオープンし、"Create new field"と入力していってください。 -## Adding a number field +## 数値フィールドの追加 {% data reusables.projects.new-field %} -1. Select **Number** ![Screenshot showing the number option](/assets/images/help/projects-v2/new-field-number.png) -1. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png) +1. **Number（数値）**を選択してください。 ![数値のオプションを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-number.png) +1. **Save（保存）**をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-save.png) -Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field." +または、{% data variables.projects.command-palette-shortcut %}を押してプロジェクトのコマンドパレットをオープンし、"Create new field"と入力していってください。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md index 94b0ea1cec..bb3bfe0db5 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md @@ -1,6 +1,6 @@ --- -title: Deleting fields -intro: 'Learn how to delete a field from your {% data variables.projects.project_v2 %}.' +title: フィールドの削除 +intro: '{% data variables.projects.project_v2 %}からフィールドを削除する方法を学んでください。' miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -10,6 +10,6 @@ topics: --- {% data reusables.projects.project-settings %} -1. Click the name of the field you want to delete. ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-single-select.png) -1. Next to the field's name, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing field name](/assets/images/help/projects-v2/field-options.png) -1. Click **Delete field**. ![Screenshot showing field name](/assets/images/help/projects-v2/delete-field.png) +1. 削除したいフィールドの名前をクリックしてください。 ![繰り返しフィールドを表示しているスクリーンショット](/assets/images/help/projects-v2/select-single-select.png) +1. フィード名の隣の{% octicon "kebab-horizontal" aria-label="The menu icon" %}をクリックしてメニューを開いてください。 ![フィールド名を表示しているスクリーンショット](/assets/images/help/projects-v2/field-options.png) +1. **Delete field（フィールドを削除）**をクリックしてください。 ![フィールド名を表示しているスクリーンショット](/assets/images/help/projects-v2/delete-field.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md index 09b569a5d0..5368b5b0f8 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md @@ -1,7 +1,7 @@ --- -title: Understanding field types -shortTitle: Understanding field types -intro: 'Learn about the different custom field types, how to add custom fields to your project, and how to manage custom fields.' +title: フィールドタイプを理解する +shortTitle: フィールドタイプを理解する +intro: 様々なカスタムフィールドについて、そしてプロジェクトへのカスタムフィールドの追加の方法、カスタムフィールドの管理の方法について学んでください。 versions: feature: projects-v2 topics: diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md index 0455d3640d..253221914c 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md @@ -1,6 +1,6 @@ --- -title: Renaming fields -intro: 'Learn about renaming existing fields in your {% data variables.projects.project_v2 %}.' +title: フィールドの名前の変更 +intro: '{% data variables.projects.project_v2 %}中の既存のフィールドの名前の変更について学んでください。' miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -10,6 +10,6 @@ topics: --- {% data reusables.projects.project-settings %} -1. Click the name of the field you want to rename. ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-single-select.png) -1. Under "Field name", type the new name for the field. ![Screenshot showing field name](/assets/images/help/projects-v2/field-rename.png) -1. To save changes, press Return. +1. 名前を変更したいフィールドの名前をクリックしてください。 ![繰り返しフィールドを表示しているスクリーンショット](/assets/images/help/projects-v2/select-single-select.png) +1. "Field name（フィールド名）"の下で、フィールドの新しい名前を入力してください。 ![フィールド名を表示しているスクリーンショット](/assets/images/help/projects-v2/field-rename.png) +1. 変更を保存するためにReturnを押してください。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md index 8207aa5d0e..415a4a3eb8 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md @@ -1,5 +1,5 @@ --- -title: 'About insights for {% data variables.product.prodname_projects_v2 %}' +title: '{% data variables.product.prodname_projects_v2 %}のインサイトについて' intro: プロジェクトのデータから構築されたグラフを表示させ、カスタマイズできます。 miniTocMaxHeadingLevel: 3 versions: @@ -17,35 +17,35 @@ allowTitleToDifferFromFilename: true {% note %} -**Note:** Historical charts are currently available as a feature preview for organizations using {% data variables.product.prodname_team %} and are generally available for organizations using {% data variables.product.prodname_ghe_cloud %}. +**ノート:** 履歴グラフは現在{% data variables.product.prodname_team %}を使用しているOrganizationでは機能プレビューとして利用でき、{% data variables.product.prodname_ghe_cloud %}を利用しているOrganizationでは一般利用可能です。 {% endnote %} {% endif %} - You can use insights for {% data variables.product.prodname_projects_v2 %} to view, create, and customize charts that use the items added to your project as their source data. デフォルトのグラフにフィルタを適用することも、独自のグラフを作成することもできます。 When you create a chart, you set the filters, chart type, the information displayed, and the chart is available to anyone that can view the project. You can generate two types of chart: current charts and historical charts. + {% data variables.product.prodname_projects_v2 %}のインサイトを使い、プロジェクトに追加したアイテムをソースデータとして利用してグラフの表示、作成、カスタマイズができます。 デフォルトのグラフにフィルタを適用することも、独自のグラフを作成することもできます。 グラフを作成する際には、フィルタ、グラフの種類、表示される情報を設定します。そのグラフは、プロジェクトを見ることができる人なら誰でも利用できます。 現在のグラフと履歴グラフという2種類のグラフを生成できます。 - ### About current charts + ### 現在のグラフについて -You can create current charts to visualize your project items. For example, you can create charts to show how many items are assigned to each individual, or how many issues are assigned to each upcoming iteration. +現在のグラフを作成して、プロジェクトのアイテムを可視化できます。 たとえば、各個人にいくつのアイテムが割り当てられているかを表示するグラフや、この先の繰り返しにいくつのIssueがアサインされているかを表示するグラフを作成できます。 -You can also use filters to manipulate the data used to build your chart. For example, you can create a chart showing how much upcoming work you have, but limit those results to particular labels or assignees. 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 +グラフを構築する溜めに使われるデータを操作するために、フィルタを使うこともできます。 たとえば、この先の作業がいくつあるのかを示すグラフを作成し、ただしその結果を特定のラベルやアサインされた人に限定することができます。 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 ![各イテレーションのアイテムの種類を表示する積み上げ列グラフのスクリーンショット](/assets/images/help/issues/column-chart-example.png) -For more information, see "[Creating charts](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts)." +詳しい情報については「[グラフの作成](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts)」を参照してください。 - ### About historical charts + ### 履歴グラフについて - Historical charts are time-based charts that allow you to view your project's trends and progress. You can view the number of items, grouped by status and other fields, over time. + 履歴グラフは時間ベースのグラフで、プロジェクトのトレンドと進捗を表示できます。 ステータスやその他のフィールドでグループ化されたアイテム数を、時間の経過とともに表示できます。 デフォルトの「バーンアップ」グラフは、時間の経過に伴うアイテムのステータスを表示し、進捗を可視化して時間の経過にともなるパターンを特定できます。 ![現在の繰り返しに対するデフォルトのバーンアップグラフの例を表示しているスクリーンショット](/assets/images/help/issues/burnup-example.png) - To create a historical chart, set your chart's X-axis to "Time." For more information, see "[Creating charts](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts)" and "[Configuring charts](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts)." + 履歴グラフを作成するには、グラフのX軸を"Time（時間）"に設定してください。 詳しい情報については「[グラフの作成](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts)」及び「[グラフの設定](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts)」を参照してください。 ## 参考リンク - [{% data variables.product.prodname_projects_v2 %}について](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects) -- "[Disabling insights for {% data variables.product.prodname_projects_v2 %} in your organization](/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization)" +- 「[Organizationでの{% data variables.product.prodname_projects_v2 %}のインサイトの無効化](/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization)」 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md index 342f88625d..bec7dbd328 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md @@ -1,6 +1,6 @@ --- -title: Configuring charts -intro: Learn how to configure your charts and filter data from your project. +title: グラフの設定 +intro: グラフを設定し、プロジェクトからのデータをフィルタリングする方法を学んでください。 miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -14,17 +14,17 @@ topics: {% note %} -**Note:** Historical charts are currently available as a feature preview. +**ノート:** 履歴グラフは現在機能プレビューとして利用できます。 {% endnote %} {% endif %} {% data reusables.projects.access-insights %} -1. In the menu on the left, click on the chart you would like to configure. ![Screenshot showing selecting a custom chart](/assets/images/help/projects-v2/insights-select-a-chart.png) -1. ページの右側で、**Configure（設定）**をクリックしてください。 パネルが右側に開きます。 ![Screenshot showing the configure button](/assets/images/help/projects-v2/insights-configure.png) -1. グラフの種類を変更するには、**Layout（レイアウト）**ドロップダウンを選択し、使いたいグラフの種類をクリックしてください。 ![Screenshot showing selecting a chart layout](/assets/images/help/projects-v2/insights-layout.png) -1. グラフのX軸として使いたいフィールドを変更するには、**X-axis（X軸）**ドロップダウンを選択し、使いたいフィールドをクリックしてください。 ![Screenshot showing selecting what to display on the x axis](/assets/images/help/projects-v2/insights-x-axis.png) -1. あるいは、X軸上のアイテムを別のフィールドでグループ化するには、**Group by（グループ化）**を選択し、使いたいフィールドをクリックするか、"None（なし）"をクリックしてグループ化を無効にしてください。 ![Screenshot showing selecting a grouping method](/assets/images/help/projects-v2/insights-group.png) -1. あるいは、プロジェクトに数値フィールドが含まれており、Y軸でそういった数値フィールドの1つの合計、平均、最小、最大を表示したい場合には、**Y-axis（Y軸）**を選択し、選択肢をクリックしてください。 として、下に現れるドロップダウンを選択し、使いたい数値フィールドをクリックしてください。 ![Screenshot showing selecting what to display on the y axis](/assets/images/help/projects-v2/insights-y-axis.png) -1. グラフを保存するには、**Save changes（変更を保存）**をクリックしてください。 ![Screenshot showing the save button](/assets/images/help/projects-v2/insights-save.png) +1. 左のメニューで、設定したいグラフをクリックしてください。 ![カスタムグラフの選択を表示しているスクリーンショット](/assets/images/help/projects-v2/insights-select-a-chart.png) +1. ページの右側で、**Configure（設定）**をクリックしてください。 パネルが右側に開きます。 ![設定ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/insights-configure.png) +1. グラフの種類を変更するには、**Layout（レイアウト）**ドロップダウンを選択し、使いたいグラフの種類をクリックしてください。 ![グラフのレイアウトの選択を表示しているスクリーンショット](/assets/images/help/projects-v2/insights-layout.png) +1. グラフのX軸として使いたいフィールドを変更するには、**X-axis（X軸）**ドロップダウンを選択し、使いたいフィールドをクリックしてください。 ![X軸に表示するものの選択を表示しているスクリーンショット](/assets/images/help/projects-v2/insights-x-axis.png) +1. あるいは、X軸上のアイテムを別のフィールドでグループ化するには、**Group by（グループ化）**を選択し、使いたいフィールドをクリックするか、"None（なし）"をクリックしてグループ化を無効にしてください。 ![グループ化の方法の選択を表示しているスクリーンショット](/assets/images/help/projects-v2/insights-group.png) +1. あるいは、プロジェクトに数値フィールドが含まれており、Y軸でそういった数値フィールドの1つの合計、平均、最小、最大を表示したい場合には、**Y-axis（Y軸）**を選択し、選択肢をクリックしてください。 として、下に現れるドロップダウンを選択し、使いたい数値フィールドをクリックしてください。 ![Y軸に表示するものの選択を表示しているスクリーンショット](/assets/images/help/projects-v2/insights-y-axis.png) +1. グラフを保存するには、**Save changes（変更を保存）**をクリックしてください。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/insights-save.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md index 14541998c7..5a2a1dfcab 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md @@ -1,6 +1,6 @@ --- -title: Creating charts -intro: Learn how to create new charts to save your configurations. +title: グラフの作成 +intro: 新しいグラフを作成して設定を保存する方法を学んでください。 miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -11,7 +11,7 @@ topics: --- {% data reusables.projects.access-insights %} -3. 左のメニューで**New chart（新規グラフ）**をクリックしてください。 ![Screenshot showing the new chart button](/assets/images/help/projects-v2/insights-new-chart.png) -4. あるいは、新しいグラフの名前を変更するには{% octicon "triangle-down" aria-label="The triangle icon" %}をクリックし、新しい名前を入力し、Returnを押してください。 ![Screenshot showing how to rename a chart](/assets/images/help/projects-v2/insights-rename.png) +3. 左のメニューで**New chart（新規グラフ）**をクリックしてください。 ![新規グラフボタンが表示されているスクリーンショット](/assets/images/help/projects-v2/insights-new-chart.png) +4. あるいは、新しいグラフの名前を変更するには{% octicon "triangle-down" aria-label="The triangle icon" %}をクリックし、新しい名前を入力し、Returnを押してください。 ![グラフの名前の変更方法を表示しているスクリーンショット](/assets/images/help/projects-v2/insights-rename.png) 5. グラフの上で、グラフを構築するのに使われたデータを変更するフィルタを入力してください。 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 -6. フィルタのテキストボックスの右で、**Save changes（変更を保存）**をクリックしてください。 ![Screenshot showing save button](/assets/images/help/projects-v2/insights-save-filter.png) +6. フィルタのテキストボックスの右で、**Save changes（変更を保存）**をクリックしてください。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/insights-save-filter.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md index 84047d3771..267a5afea9 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md @@ -1,6 +1,6 @@ --- -title: 'Viewing insights from your {% data variables.projects.project_v2 %}' -shortTitle: Viewing insights +title: '{% data variables.projects.project_v2 %}のインサイトの表示' +shortTitle: インサイトの表示 intro: ... versions: feature: projects-v2 diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md index c7595f2857..c2bf8fb3f7 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md @@ -32,7 +32,7 @@ Issueは様々な方法で作成できるので、ワークフローで最も便 プロジェクトで、Issueを整理して優先順位付けできます。 {% ifversion fpt or ghec %}大きなIssueの一部であるIssueを追跡するには、タスクリストが使えます。{% endif %}関連するIssueを分類するには、ラベルとマイルストーンが使えます。 -For more information about projects, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." {% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %} {% ifversion fpt or ghec %}For more information about task lists, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." {% endif %}ラベルとマイルストーンに関する詳しい情報については「[作業を追跡するためのラベルとマイルストーンの利用](/issues/using-labels-and-milestones-to-track-work)」を参照してください。 +プロジェクトに関する詳しい情報については{% ifversion projects-v2 %}「[プロジェクトについて](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)」 {% else %}「[プロジェクトボードで作業の整理](/issues/organizing-your-work-with-project-boards)」{% endif %}を参照してください。{% ifversion fpt or ghec %}タスクリストに関する詳しい情報については「[タスクリストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)」を参照してください。 {% endif %}ラベルとマイルストーンに関する詳しい情報については「[作業を追跡するためのラベルとマイルストーンの利用](/issues/using-labels-and-milestones-to-track-work)」を参照してください。 ## 最新情報の確認 diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md index f4c2ab30cb..e751ab3fbb 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md @@ -43,7 +43,7 @@ Pull Requestの説明もしくはコミットメッセージ中でサポート * fix * fixes * fixed -* 解決 +* resolve * resolves * resolved diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md index f71e3526c1..c436e96ae1 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md @@ -1,6 +1,6 @@ --- -title: Teamもしくはプロジェクトの作業の計画と追跡 -intro: '{% data variables.product.prodname_dotcom %}の計画及び追跡ツールを使って、Teamあるいはプロジェクトの作業を管理するために必要なこと。' +title: Planning and tracking work for your team or project +intro: 'The essentials for using {% data variables.product.prodname_dotcom %}''s planning and tracking tools to manage work on a team or project.' versions: fpt: '*' ghes: '*' @@ -11,120 +11,119 @@ topics: - Project management - Projects --- +## Introduction +You can use {% data variables.product.prodname_dotcom %} repositories, issues, project boards, and other tools to plan and track your work, whether working on an individual project or cross-functional team. -## はじめに -個別のプロジェクトで作業しているにしても、機能横断的なチームで作業しているにしても、{% data variables.product.prodname_dotcom %}のリポジトリ、Issue、プロジェクトボードやその他のツールを使って作業の計画と追跡ができます。 +In this guide, you will learn how to create and set up a repository for collaborating with a group of people, create issue templates{% ifversion fpt or ghec %} and forms{% endif %}, open issues and use task lists to break down work, and establish a project board for organizing and tracking issues. -このガイドでは、人々のグループとコラボレーションするためのリポジトリの作成とセットアップ、Issueテンプレート{% ifversion fpt or ghec %}及びフォーム{% endif %}の作成、Issueのオープンと作業をブレークダウンするためのタスクリストの利用、Issueを整理して追跡するためのプロジェクトボードの設置の方法を学びます。 +## Creating a repository +When starting a new project, initiative, or feature, the first step is to create a repository. Repositories contain all of your project's files and give you a place to collaborate with others and manage your work. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)." -## リポジトリを作成する -新しいプロジェクト、イニシアティブ、機能を開始するとき、最初のステップはリポジトリの作成です。 リポジトリにはプロジェクトのすべてのファイルが含まれ、他者とコラボレーションしたり、作業を管理したりする場所を提供します。 詳しい情報については「[新しいリポジトリの作成](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)」を参照してください。 +You can set up repositories for different purposes based on your needs. The following are some common use cases: -必要に応じて、様々な目的のためにリポジトリをセットアップできます。 以下は、いくつかの一般的なユースケースです。 +- **Product repositories**: Larger organizations that track their work and goals around specific products may have one or more repositories containing the code and other files. These repositories can also be used for documentation, reporting on product health or future plans for the product. +- **Project repositories**: You can create a repository for an individual project you are working on, or for a project you are collaborating on with others. For an organization that tracks work for short-lived initiatives or projects, such as a consulting firm, there is a need to report on the health of a project and move people between different projects based on skills and needs. Code for the project is often contained in a single repository. +- **Team repositories**: For an organization that groups people into teams, and brings projects to them, such as a dev tools team, code may be scattered across many repositories for the different work they need to track. In this case it may be helpful to have a team-specific repository as one place to track all the work the team is involved in. +- **Personal repositories**: You can create a personal repository to track all your work in one place, plan future tasks, or even add notes or information you want to save. You can also add collaborators if you want to share this information with others. -- **製品リポジトリ**: 特定の製品に関する作業とゴールを追跡する大規模な組織は、そのコードや他のファイルを含む1つ以上のリポジトリを持つことがあります。 それらのリポジトリは、ドキュメンテーション、製品の改善性、あるいは製品の将来の計画のためにも使われることがあります。 -- **プロジェクトリポジトリ**: 作業をしている個々のプロジェクト、あるいは他者とコラボレーションしているプロジェクトのためにリポジトリを作成することができます。 短期間のイニシアティブやプロジェクトなどのための作業を追跡する、たとえばコンサルティングファームなどの組織では、プロジェクトの健全性に関するレポートや、人々をスキルや要求に応じて様々なプロジェクト間で移動させる必要があります。 こうしたプロジェクトのためのコードは、多くの場合1つのリポジトリに含まれます。 -- **チームリポジトリ**: 人々をチームにグループ化し、開発ツールチームのようなそれらのグループにプロジェクトを割り当てるような組織では、コードは追跡しなければならない様々な作業に対する多くのリポジトリに分散されるかもしれません。 この場合、そのチームが関わるすべての作業を追跡するための1つの場所として、チーム固有のリポジトリを持つとよいかもしれません。 -- **個人リポジトリ**: 個人リポジトリを作成して、自分のすべての作業を1カ所で追跡し、将来のタスクを計画し、さらには保存しておきたいノートや情報を追加しておくことさえできます。 この情報を他者と共有したい場合は、コラボレータを追加することもできます。 +You can create multiple, separate repositories if you want different access permissions for the source code and for tracking issues and discussions. For more information, see "[Creating an issues-only repository](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-an-issues-only-repository)." -ソースコードに様々なアクセス権限を設定し、Issueやディスカッションを追跡したい場合には、複数の個別のリポジトリを作成することもできます。 詳しい情報については「[Issueのみのリポジトリの作成](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-an-issues-only-repository)」を参照してください。 +For the following examples in this guide, we will be using an example repository called Project Octocat. +## Communicating repository information +You can create a README.md file for your repository to introduce your team or project and communicate important information about it. A README is often the first item a visitor to your repository will see, so you can also provide information on how users or contributors can get started with the project and how to contact the team. For more information, see "[About READMEs](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes)." -このガイドの以下の例では、Projet Octocatというサンプルリポジトリを使います。 -## リポジトリ情報のコミュニケーション -リポジトリにREADME.mdファイルを追加して、Teamやプロジェクトを紹介し、それらに関する重要な情報を伝えることができます。 リポジトリにアクセスした人が最初に見るのはREADMEのことが多いので、ユーザやコントリビュータがプロジェクトとどのように関わり始めたらいいのか、そしてチームとどのように連絡を取ればいいのかに関する情報を提供することもできます。 詳細は「[README について](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes)」を参照してください。 +You can also create a CONTRIBUTING.md file specifically to contain guidelines on how users or contributors can contribute and interact with the team or project, such as how to open a bug fix issue or request an improvement. For more information, see "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)." +### README example +We can create a README.md to introduce our new project, Project Octocat. -特に、バグ修正のIssueのオープンや改善のリクエストの方法といった、ユーザやコントリビュータがチームやプロジェクトに貢献して関わるやりかたのガイドラインを含む、CONTRIBUTING.mdファイルを作成することもできます。 詳しい情報については、「[リポジトリコントリビューターのためのガイドラインを定める](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)」を参照してください。 -### README の例 -新しいプロジェクトであるProject Octocatを紹介するREADME.mdを作成できます。 +![Creating README example](/assets/images/help/issues/quickstart-creating-readme.png) +## Creating issue templates -![READMEの例の作成](/assets/images/help/issues/quickstart-creating-readme.png) -## Issue テンプレートを作成する +You can use issues to track the different types of work that your cross-functional team or project covers, as well as gather information from those outside of your project. The following are a few common use cases for issues. -Issueを使って、機能横断的なチームやプロジェクトがカバーする様々な種類の作業を追跡したり、プロジェクト外のチームやプロジェクトから情報を集めることができます。 以下は、いくつかの一般的なIssueのユースケースです。 +- Release tracking: You can use an issue to track the progress for a release or the steps to complete the day of a launch. +- Large initiatives: You can use an issue to track progress on a large initiative or project, which is then linked to the smaller issues. +- Feature requests: Your team or users can create issues to request an improvement to your product or project. +- Bugs: Your team or users can create issues to report a bug. -- リリース追跡: Issueを使って、リリースやローンチ日を完了させるステップの進捗を追跡できます。 -- 大規模なイニシアティブ: Issueを使って、大規模なイニシアティブやプロジェクトの進捗を追跡できます。それらは、より小さなIssueにリンクされます。 -- 機能リクエスト: チームやユーザは、Issueを作成して製品やプロジェクトに改善をリクエストできます。 -- バグ: チームやユーザは、Issueを作成してバグを報告できます。 +Depending on the type of repository and project you are working on, you may prioritize certain types of issues over others. Once you have identified the most common issue types for your team, you can create issue templates {% ifversion fpt or ghec %}and forms{% endif %} for your repository. Issue templates {% ifversion fpt or ghec %}and forms{% endif %} allow you to create a standardized list of templates that a contributor can choose from when they open an issue in your repository. For more information, see "[Configuring issue templates for your repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository)." -作業をしているリポジトリやプロジェクトの種類によっては、特定の種類のIssueを他よりも優先することになるかもしれません。 チームで最も一般的なIssueの種類を特定できたら、リポジトリにIssueテンプレート{% ifversion fpt or ghec %}やフォーム{% endif %}を作成できます。 Issueテンプレート{% ifversion fpt or ghec %}とフォーム{% endif %}を使うと、リポジトリでIssueをオープンするときにコントリビューターが選択できる標準化されたテンプレートのリストを作成できます。 詳しい情報については、「[リポジトリ用に Issue テンプレートを設定する](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository)」を参照してください。 +### Issue template example +Below we are creating an issue template for reporting a bug in Project Octocat. -### Issueテンプレートの例 -以下、Project OctocatでバグレポートのためのIssueテンプレートを作成しています。 +![Creating issue template example](/assets/images/help/issues/quickstart-creating-issue-template.png) -![Issueテンプレートの例の作成](/assets/images/help/issues/quickstart-creating-issue-template.png) +Now that we created the bug report issue template, you are able to select it when creating a new issue in Project Octocat. -バグレポートのIssueテンプレートを作成したので、新しいIssueをProject Octocatで作成する際に選択できるようになりました。 +![Choosing issue template example](/assets/images/help/issues/quickstart-issue-creation-menu-with-template.png) -![Issueテンプレートの例の選択](/assets/images/help/issues/quickstart-issue-creation-menu-with-template.png) +## Opening issues and using task lists to track work +You can organize and track your work by creating issues. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)." +### Issue example +Here is an example of an issue created for a large initiative, front-end work, in Project Octocat. -## Issueのオープンとタスクリストを使用した作業の追跡 -Issueを作成することで、作業を整理し、追跡できます。 詳しい情報については、「[Issue を作成する](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)」を参照してください。 -### Issueの例 -以下は、Project Octocatの大規模なイニシアティブであるフロントエンドの作業のために作成されたIssueの例です。 +![Creating large initiative issue example](/assets/images/help/issues/quickstart-create-large-initiative-issue.png) +### Task list example -![大規模なイニシアティブのissueの例の作成](/assets/images/help/issues/quickstart-create-large-initiative-issue.png) -### タスクリストの例 +You can use task lists to break larger issues down into smaller tasks and to track issues as part of a larger goal. {% ifversion fpt or ghec %} Task lists have additional functionality when added to the body of an issue. You can see the number of tasks completed out of the total at the top of the issue, and if someone closes an issue linked in the task list, the checkbox will automatically be marked as complete.{% endif %} For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." -タスクリストを使って、大きなIssueを小さなタスクに分割し、大きなゴールの一部としてIssueを追跡できます。 {% ifversion fpt or ghec %}Issueの本体に追加されたタスクリストには、追加の機能があります。 Issueの上部では全体の中で完了したタスク数を見ることができ、誰かがタスクリストにリンクされたIssueをクローズすると、そのチェックボックスは自動的に完了としてマークされます。{% endif %}詳しい情報については「[タスクリストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)」を参照してください。 +Below we have added a task list to our Project Octocat issue, breaking it down into smaller issues. -以下では、Project OctocatのIssueにタスクリストを追加し、小さなIssueに分割しました。 +![Adding task list to issue example](/assets/images/help/issues/quickstart-add-task-list-to-issue.png) -![Issueの例へのタスクリストの追加](/assets/images/help/issues/quickstart-add-task-list-to-issue.png) +## Making decisions as a team +You can use issues and discussions to communicate and make decisions as a team on planned improvements or priorities for your project. Issues are useful when you create them for discussion of specific details, such as bug or performance reports, planning for the next quarter, or design for a new initiative. Discussions are useful for open-ended brainstorming or feedback, outside the codebase and across repositories. For more information, see "[Which discussion tool should I use?](/github/getting-started-with-github/quickstart/communicating-on-github#which-discussion-tool-should-i-use)." -## チームとしての意思決定 -Issueやディスカッションを使い、プロジェクトの計画された改善や優先順位についてコミュニケーションを取り、チームとして意思決定することができます。 Issueは、バグやパフォーマンスレポート、次の四半期の計画、新しいイニシアティブのデザインといった、特定の詳細に関するディスカッションのために作成すると役立ちます。 ディスカッションは、コードベース外でリポジトリをまたぐオープンエンドのブレインストーミングやフィードバックのために役立ちます。 詳しい情報については「[どのディスカッションツールを使うべきでしょうか？](/github/getting-started-with-github/quickstart/communicating-on-github#which-discussion-tool-should-i-use)」を参照してください。 +As a team, you can also communicate updates on day-to-day tasks within issues so that everyone knows the status of work. For example, you can create an issue for a large feature that multiple people are working on, and each team member can add updates with their status or open questions in that issue. +### Issue example with project collaborators +Here is an example of project collaborators giving a status update on their work on the Project Octocat issue. -チームとして、Issue内の日々のタスクの更新についてコミュニケーションを取り、全員に作業の状況を知らせることができます。 たとえば、複数の人が作業をしている大きな機能についてのIssueを作成し、各チームメンバーがそのIssue内で状況を更新したり質問を投げたりできるようにすることができます。 -### プロジェクトのコラボレータとのIssueの例 -以下は、Project OctocatのIssueで作業状況を更新するプロジェクトのコラボレータの例です。 +![Collaborating on issue example](/assets/images/help/issues/quickstart-collaborating-on-issue.png) +## Using labels to highlight project goals and status +You can create labels for a repository to categorize issues, pull requests, and discussions. {% data variables.product.prodname_dotcom %} also provides default labels for every new repository that you can edit or delete. Labels are useful for keeping track of project goals, bugs, types of work, and the status of an issue. -![Issueの例でのコラボレーション](/assets/images/help/issues/quickstart-collaborating-on-issue.png) -## プロジェクトのゴールとステータスをハイライトするためのラベルの利用 -Issue、Pull Request、ディスカッションを分類するために、リポジトリにラベルを作成できます。 {% data variables.product.prodname_dotcom %}は、すべての新しいリポジトリにデフォルトのラベルを提供します。それらは編集したり削除したりできます。 ラベルは、プロジェクトのゴール、バグ、作業の種類、Issueのステータスを追跡するための役に立ちます。 +For more information, see "[Creating a label](/issues/using-labels-and-milestones-to-track-work/managing-labels#creating-a-label)." -詳細は「[ラベルの作成](/issues/using-labels-and-milestones-to-track-work/managing-labels#creating-a-label)」を参照してください。 +Once you have created a label in a repository, you can apply it on any issue, pull request or discussion in the repository. You can then filter issues and pull requests by label to find all associated work. For example, find all the front end bugs in your project by filtering for issues with the `front-end` and `bug` labels. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)." +### Label example +Below is an example of a `front-end` label that we created and added to the issue. -リポジトリにラベルを作成すると、それはリポジトリ内の任意のIssue、Pull Request、ディスカッションに適用できます。 そして、すべての関連する作業を見つけるためにラベルでIssueやPull Requestをフィルタリングできます。 たとえば、Issueを`front-end`及び`bug`というラベルでフィルタリングし、すべてのフロントエンドのバグを見つけることができます。 詳しい情報については「[IssueやPull Requestのフィルタリングと検索](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)」を参照してください。 -### ラベルの例 -以下は、作成した`front-end`の例で、Issueに追加されています。 +![Adding a label to an issue example](/assets/images/help/issues/quickstart-add-label-to-issue.png) -![Issueの例へのラベルの追加](/assets/images/help/issues/quickstart-add-label-to-issue.png) - -## プロジェクトボードへのIssueの追加 +## Adding issues to a project board {% ifversion projects-v2 %} -You can use {% data variables.projects.projects_v2 %} on {% data variables.product.prodname_dotcom %} to plan and track the work for your team. プロジェクトはカスタマイズ可能なスプレッドシートで、{% data variables.product.prodname_dotcom %}上のIssueやPull Requestと統合されており、自動的に{% data variables.product.prodname_dotcom %}上の情報を最新の状態に保ちます。 IssueやPull Requestのフィルタリング、ソート、グループ化によってレイアウトをカスタマイズできます。 To get started with projects, see "[Quickstart for projects](/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects)." +You can use {% data variables.projects.projects_v2 %} on {% data variables.product.prodname_dotcom %} to plan and track the work for your team. A project is a customizable spreadsheet that integrates with your issues and pull requests on {% data variables.product.prodname_dotcom %}, automatically staying up-to-date with the information on {% data variables.product.prodname_dotcom %}. You can customize the layout by filtering, sorting, and grouping your issues and PRs. To get started with projects, see "[Quickstart for projects](/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects)." ### Project example -以下は、作成したProject OctocatのIssueが展開されたサンプルプロジェクトの表レイアウトのビューです。 +Here is the table layout of an example project, populated with the Project Octocat issues we have created. ![Projects table layout example](/assets/images/help/issues/quickstart-projects-table-view.png) -同じプロジェクトをボードとして見ることもできます。 +We can also view the same project as a board. ![Projects board layout example](/assets/images/help/issues/quickstart-projects-board-view.png) {% endif %} {% ifversion projects-v1 %} -You can {% ifversion projects-v2 %} also use the existing{% else %} use{% endif %} {% data variables.product.prodname_projects_v1 %} on {% data variables.product.prodname_dotcom %} to plan and track your or your team's work. プロジェクトボードは、Issue、プルリクエスト、選択した列内でカードとして分類されるノートから構成されます。 機能の作業、高レベルのロードマップ、さらにはリリースチェックリストのためにプロジェクトボードを作成できます。 詳細は「[プロジェクトボードについて](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)」を参照してください。 -### プロジェクトボードの例 -以下は、サンプルのProject Octocatのプロジェクトボードで、作成したIssueと、そのIssueをブレークダウンした小さなIssueが追加されています。 +You can {% ifversion projects-v2 %} also use the existing{% else %} use{% endif %} {% data variables.product.prodname_projects_v1 %} on {% data variables.product.prodname_dotcom %} to plan and track your or your team's work. Project boards are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can create project boards for feature work, high-level roadmaps, or even release checklists. For more information, see "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." +### Project board example +Below is a project board for our example Project Octocat with the issue we created, and the smaller issues we broke it down into, added to it. -![プロジェクトボードの例](/assets/images/help/issues/quickstart-project-board.png) +![Project board example](/assets/images/help/issues/quickstart-project-board.png) {% endif %} -## 次のステップ +## Next steps -これで、作業の計画と追跡のために{% data variables.product.prodname_dotcom %}が提供するツールについて学び、機能横断的なチームやプロジェクトのリポジトリのセットアップを始めることができました！ 以下は、さらにリポジトリをカスタマイズし、作業を整理するのに役立つリソースです。 +You have now learned about the tools {% data variables.product.prodname_dotcom %} offers for planning and tracking your work, and made a start in setting up your cross-functional team or project repository! Here are some helpful resources for further customizing your repository and organizing your work. -- リポジトリの作成についてさらに学ぶための「[リポジトリについて](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)」 -- Issueの作成と管理のための様々な方法を学ぶための「[Issueでの作業の追跡](/issues/tracking-your-work-with-issues)」 -- Issueテンプレートについてさらに学ぶための「[IssueとPull Requestテンプレートについて](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)」 -- ラベルの作成、編集、削除の方法を学ぶための「[ラベルの管理](/issues/using-labels-and-milestones-to-track-work/managing-labels)」 -- タスクリストについてさらに学ぶための「[タスクリストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)」 +- "[About repositories](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)" for learning more about creating repositories +- "[Tracking your work with issues](/issues/tracking-your-work-with-issues)" for learning more about different ways to create and manage issues +- "[About issues and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)" for learning more about issue templates +- "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)" for learning how to create, edit and delete labels +- "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)" for learning more about task lists {% ifversion projects-v2 %} - "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)" for learning more about projects - "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)" for learning how to customize views for projects{% endif %} {% ifversion projects-v1 %}- "[About {% data variables.product.prodname_projects_v1 %}](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)" for learning how to manage project boards{% endif %} diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md index b93003199f..5e22f4ebb3 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md @@ -71,7 +71,7 @@ Issueを分類するために、ラベルを追加してください。 たと ## プロジェクトへのIssueの追加 -You can add the issue to an existing project{% ifversion projects-v2 %} and populate metadata for the project. {% endif %} For more information about projects, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."{% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %} +Issueを既存のプロジェクトに追加{% ifversion projects-v2 %}してプロジェクトのメタデータを展開 {% endif %}できます。プロジェクトに関する詳しい情報については{% ifversion projects-v2 %}「[プロジェクトについて](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)」{% else %}「[プロジェクトボードでの作業の整理](/issues/organizing-your-work-with-project-boards)」{% endif %}を参照してください。 ![プロジェクトを持つIssue](/assets/images/help/issues/issue-project.png) @@ -97,5 +97,5 @@ Issueは、幅広い目的で使用できます。 例: {% data variables.product.prodname_github_issues %} で次のステップに進む際に役立つ、以下のようなリソースを参照してください。 - Issueについてさらに学ぶには「[Issueについて](/issues/tracking-your-work-with-issues/about-issues)」を参照してください。 -- To learn more about how projects can help you with planning and tracking, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."{% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %} +- プロジェクトがどのように計画と追跡に役立つかについてさらに学ぶには、{% ifversion projects-v2 %}「[プロジェクトについて](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)」{% else %}「[プロジェクトボードでの作業の整理](/issues/organizing-your-work-with-project-boards)」{% endif %}を参照してください。 - Issueテンプレート{% ifversion fpt or ghec %}及びIssueフォーム{% endif %}を利用して、コントリビューターが特定の情報を提供してくれるよう促進することについてさらに学ぶには「[IssueやPull Requestが役立つものになるよう促進するためのテンプレートの利用](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)」を参照してください。 diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md index bae593ce4b..fe79929e80 100644 --- a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md +++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md @@ -15,21 +15,21 @@ shortTitle: Organizationのプロフィールのカスタマイズ ## Organization のプロフィールページについて {% ifversion org-profile-pin-private %} -You can customize your organization's Overview page to show a README and pinned repositories dedicated to public users or members of the organization. +Organizationの概要ページをカスタマイズして、一般ユーザもしくはOrganizationのメンバー専用のREADMEと固定リポジトリを表示させることができます。 -![Image of a public organization profile page](/assets/images/help/organizations/public_profile.png) +![パブリックのOrganizationプロフィールページの画像](/assets/images/help/organizations/public_profile.png) -Members of your organization who are signed into {% data variables.product.prodname_dotcom %}, can select a `member` or `public` view of the README and pinned repositories when they visit your organization's profile page. +{% data variables.product.prodname_dotcom %}にサインインしたOrganizationのメンバーは、Organizationのプロフィールページにアクセスした際に、READMEと固定リポジトリの`member`もしくは`public`ビューを選択できます。 -![Image of a public organization profile page view context switcher](/assets/images/help/organizations/profile_view_switcher_public.png) +![パブリックのOrganizationプロフィールページのコンテキストスイッチャーの画像](/assets/images/help/organizations/profile_view_switcher_public.png) -The view defaults to `member` if either a members-only README or members-only pinned repositories are present, and `public` otherwise. +メンバー専用のREADMEあるいはメンバー専用の固定リポジトリがある場合は`member`がデフォルトであり、そうでない場合は`public`がデフォルトになります。 -![Image of a members only organization profile page](/assets/images/help/organizations/member_only_profile.png) +![メンバー専用のOrganizationプロフィールページの画像](/assets/images/help/organizations/member_only_profile.png) -Users who are not members of your organization will be shown a `public` view. +Organizationのメンバーではないユーザには、`public`ビューが表示されます。 -### Pinned repositories +### 固定リポジトリ 最大で一般ユーザに対し6つのリポジトリ、そしてOrganizationのメンバーに対して6つのリポジトリを選択することによって、ユーザに対して重要なリポジトリや頻繁に利用されるリポジトリへアクセスを容易にできます。 Organizationのプロフィールにリポジトリを固定すると、"Pinned（ピン止め）"セクションがプロフィールページの"Repositories（リポジトリ）"セクションの上部に表示されます。 @@ -64,24 +64,24 @@ OrganizationのプロフィールのREADMEにどういった情報を含める 2. Organizationの`.github-private`リポジトリで、`profile`フォルダ内に`README.md`というファイルを作成してください。 3. `README.md`ファイルへの変更をコミットしてください。 `README.md`の内容は、Organizationプロフィールのメンバービューに表示されます。 - ![Image of an organization's member-only README](/assets/images/help/organizations/org_member_readme.png) + ![Organizationのメンバー専用READMEの画像](/assets/images/help/organizations/org_member_readme.png) -## Organizationのプロフィールへのリポジトリのピン止め +## Organizationのプロフィールへのリポジトリの固定 -頻繁に使われるようなリポジトリなど、強調したいリポジトリをOrganizationのプロフィールページにピン止めできます。 Organizaitonのプロフィールにピン止めするリポジトリを選択するには、Organizationのオーナーでなければなりません。 +頻繁に使われるようなリポジトリなど、強調したいリポジトリをOrganizationのプロフィールページに固定できます。 Organizaitonのプロフィールに固定するリポジトリを選択するには、Organizationのオーナーでなければなりません。 1. Organizationのプロフィールページにアクセスしてください。 2. ページの右のサイドバー内の{% octicon "eye" aria-label="The eye octicon" %} "View as"リンク内で、ドロップダウンメニューから**Public（公開）**もしくは**Member（メンバー）**プロフィールビューを選択してください。 ![Organizationプロフィールビューのドロップダウンの画像](/assets/images/help/organizations/org_profile_view.png) -3. ピン止めされたリポジトリのセクションで、**Customize pins（ピン止めのカスタマイズ）**を選択してください。 +3. 固定リポジトリのセクションで、**Customize pins（固定のカスタマイズ）**を選択してください。 ![ピン止めのカスタマイズリンクの画像](/assets/images/help/organizations/customize_pins_link.png) - - まだOrganizationのプロフィールにピン止めしたリポジトリがないなら、代わりにプロフィールページの右のサイドバーにある**pin repositories（リポジトリのピン止め）**をクリックしなければなりません。 ![右のサイドバーにあるリポジトリのピン止めリンクの画像](/assets/images/help/organizations/pin_repositories_link.png) + - まだOrganizationのプロフィールに固定リポジトリがないなら、代わりにプロフィールページの右のサイドバーにある**pin repositories（リポジトリの固定）**をクリックしなければなりません。 ![右のサイドバーにあるリポジトリのピン止めリンクの画像](/assets/images/help/organizations/pin_repositories_link.png) -4. "Edit pinned repositories（ピン止めされたリポジトリの編集）"ダイアログボックスで、最大で6つの表示するパブリック、{% ifversion not fpt %}プライベート、もしくはインターナル{% else %}もしくはプライベート{% endif %}リポジトリの組み合わせを選択してください。 +4. "Edit pinned repositories（固定リポジトリの編集）"ダイアログボックスで、最大で6つの表示するパブリック、{% ifversion not fpt %}プライベート、もしくはインターナル{% else %}もしくはプライベート{% endif %}リポジトリの組み合わせを選択してください。 ![ピン止めされたリポジトリダイアログの画像](/assets/images/help/organizations/pinned_repo_dialog.png) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md index 90a1037c57..cac3872bad 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md @@ -1,6 +1,6 @@ --- -title: 'Adding an outside collaborator to a {% data variables.product.prodname_project_v1 %} in your organization' -intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can add an outside collaborator and customize their permissions to a {% data variables.projects.projects_v1_board %}.' +title: 'Organizationの{% data variables.product.prodname_project_v1 %}への外部のコラボレータの追加' +intro: 'Organizationのオーナーもしくは{% data variables.projects.projects_v1_board %}の管理者は、{% data variables.projects.projects_v1_board %}に外部のコラボレータを追加してその権限をカスタマイズできます。' redirect_from: - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization @@ -18,7 +18,7 @@ allowTitleToDifferFromFilename: true {% data reusables.projects.project_boards_old %} -An outside collaborator is a person who isn't explicitly a member of your organization, but who has permissions to a {% data variables.projects.projects_v1_board %} in your organization. +外部のコラボレータは Organization の明示的なメンバーではありませんが、Organizationの{% data variables.projects.projects_v1_board %}への権限を持っています。 {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md index 151b332f3b..fe90d2cf81 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md @@ -1,6 +1,6 @@ --- -title: 'Managing access to your organization’s {% data variables.product.prodname_projects_v1 %}' -intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give organization members, teams, and outside collaborators different levels of access to {% data variables.projects.projects_v1_boards %} owned by your organization.' +title: 'Organizationの{% data variables.product.prodname_projects_v1 %}へのアクセス管理' +intro: 'Organization のオーナーまたは{% data variables.projects.projects_v1_board %}の管理者は、Organization が所有する{% data variables.projects.projects_v1_boards %}について、Organization のメンバー、チーム、外部のコラボレータごとに異なるレベルのアクセス権を付与できます。' redirect_from: - /articles/managing-access-to-your-organization-s-project-boards - /articles/managing-access-to-your-organizations-project-boards @@ -20,7 +20,7 @@ children: - /managing-an-individuals-access-to-an-organization-project-board - /adding-an-outside-collaborator-to-a-project-board-in-your-organization - /removing-an-outside-collaborator-from-an-organization-project-board -shortTitle: 'Manage {% data variables.product.prodname_project_v1 %} access' +shortTitle: '{% data variables.product.prodname_project_v1 %}アクセスの管理' allowTitleToDifferFromFilename: true --- diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md index 4d15a9b801..d864160caa 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md @@ -1,6 +1,6 @@ --- -title: 'Managing access to a {% data variables.product.prodname_project_v1 %} for organization members' -intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can set a default permission level for a {% data variables.projects.projects_v1_board %} for all organization members.' +title: 'Organizationのメンバーに対する{% data variables.product.prodname_project_v1 %}へのアクセスの管理' +intro: 'Organizationのオーナーまたは{% data variables.projects.projects_v1_board %}の管理者は、すべてのOrganizationメンバーに対して{% data variables.projects.projects_v1_board %}へのデフォルトの権限レベルを設定できます。' redirect_from: - /articles/managing-access-to-a-project-board-for-organization-members - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members @@ -18,13 +18,13 @@ allowTitleToDifferFromFilename: true {% data reusables.projects.project_boards_old %} -By default, organization members have write access to their organization's {% data variables.projects.projects_v1_boards %} unless organization owners or {% data variables.projects.projects_v1_board %} admins set different permissions for specific {% data variables.projects.projects_v1_boards %}. +デフォルトでは、Organization のメンバーはその Organization の{% data variables.projects.projects_v1_boards %}に対する書き込みアクセスを持ちます。ただし、Organization のオーナーまたは{% data variables.projects.projects_v1_board %}の管理者が、特定の{% data variables.projects.projects_v1_boards %}に異なる権限を設定している場合は例外です。 ## Organization のすべてのメンバーに対して標準の権限レベルを設定する {% tip %} -**Tip:** You can give an organization member higher permissions to {% data variables.projects.projects_v1_board %}. 詳しい情報については、「[Organization のプロジェクトボードの権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 +**参考:** Organizationのメンバーに{% data variables.projects.projects_v1_board %}へのより高い権限を付与することができます。 詳しい情報については、「[Organization のプロジェクトボードの権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 {% endtip %} @@ -40,6 +40,6 @@ By default, organization members have write access to their organization's {% da ## 参考リンク -- "[Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-an-individual-s-access-to-an-organization-project-board)" -- "[Managing team access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-team-access-to-an-organization-project-board)" +- 「[Organizationの{% data variables.product.prodname_project_v1 %}への個人のアクセスの管理](/articles/managing-an-individual-s-access-to-an-organization-project-board)」 +- 「[Organizationの{% data variables.product.prodname_project_v1 %}への Team のアクセスの管理](/articles/managing-team-access-to-an-organization-project-board)」 - 「[Organizationの{% data variables.product.prodname_project_v1_caps %}の権限](/articles/project-board-permissions-for-an-organization)」 diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md index 93946c2fba..95c070f450 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md @@ -1,6 +1,6 @@ --- -title: 'Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}' -intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can manage an individual member''s access to a {% data variables.projects.projects_v1_board %} owned by your organization.' +title: '{% data variables.product.prodname_project_v1 %}への個人のアクセス管理' +intro: 'Organization のオーナーまたは{% data variables.projects.projects_v1_board %}の管理者は、Organization が所有する{% data variables.projects.projects_v1_board %}への個々のメンバーのアクセスを管理できます。' redirect_from: - /articles/managing-an-individual-s-access-to-an-organization-project-board - /articles/managing-an-individuals-access-to-an-organization-project-board @@ -21,11 +21,11 @@ allowTitleToDifferFromFilename: true {% note %} -**Note:** {% data reusables.project-management.cascading-permissions %} For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." +**ノート:** {% data reusables.project-management.cascading-permissions %} 詳しい情報については「[Organizatonの{% data variables.product.prodname_project_v1_caps %}の権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 {% endnote %} -## Giving an organization member access to a {% data variables.projects.projects_v1_board %} +## Organizationのメンバーへの{% data variables.projects.projects_v1_board %}に対するアクセスの付与 {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} @@ -39,7 +39,7 @@ allowTitleToDifferFromFilename: true {% data reusables.project-management.add-collaborator %} {% data reusables.project-management.collaborator-permissions %} -## Changing an organization member's access to a {% data variables.projects.projects_v1_board %} +## {% data variables.projects.projects_v1_board %}へのOrganizationメンバーのアクセスの変更 {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} @@ -51,9 +51,9 @@ allowTitleToDifferFromFilename: true {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.collaborator-permissions %} -## Removing an organization member's access to a {% data variables.projects.projects_v1_board %} +## {% data variables.projects.projects_v1_board %}へのOrganizationのメンバーのアクセスの削除 -When you remove a collaborator from a {% data variables.projects.projects_v1_board %}, they may still retain access to the board based on the permissions they have for other roles. To completely remove access to a {% data variables.projects.projects_v1_board %}, you must remove access for each role the person has. For instance, a person may have access to the {% data variables.projects.projects_v1_board %} as an organization member or team member. 詳しい情報については[Organizationの{% data variables.product.prodname_project_v1_caps %}の権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 +{% data variables.projects.projects_v1_board %}からコラボレータを削除しても、コラボレータは引き続き他のロールの権限に基づきボードにアクセスできることがあります。 {% data variables.projects.projects_v1_board %}へのアクセスを完全に削除するには、その人が持っている各ロールのアクセスを削除しなければなりません。 たとえば、ある人は{% data variables.projects.projects_v1_board %}へのアクセスをOrganizationのメンバーあるいはTeamのメンバーとして持っているかもしれません。 詳しい情報については[Organizationの{% data variables.product.prodname_project_v1_caps %}の権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md index 68240bbaa3..e48de84cea 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md @@ -1,6 +1,6 @@ --- -title: 'Managing team access to an organization {% data variables.product.prodname_project_v1 %}' -intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give a team access to a {% data variables.projects.projects_v1_board %} owned by your organization.' +title: 'Organizationの{% data variables.product.prodname_project_v1 %}へのTeamアクセスの管理' +intro: 'Organization のオーナーまたは{% data variables.projects.projects_v1_board %}の管理者は、Organizationが所有する{% data variables.projects.projects_v1_board %}へのアクセスをTeamに付与できます。' redirect_from: - /articles/managing-team-access-to-an-organization-project-board - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board @@ -21,18 +21,18 @@ allowTitleToDifferFromFilename: true {% warning %} **警告:** -- You can change a team's permission level if the team has direct access to a {% data variables.projects.projects_v1_board %}. If the team's access to the {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %}. -- If you add or remove {% data variables.projects.projects_v1_board %} access for a parent team, each of that parent's child teams will also receive or lose access to the {% data variables.projects.projects_v1_board %}. 詳しい情報については[Team について](/articles/about-teams)を参照してください。 +- Teamが{% data variables.projects.projects_v1_board %}への直接のアクセスを持っているなら、Teamの権限レベルを変更できます。 {% data variables.projects.projects_v1_board %}へのTeamのアクセスが親チームから継承されたものなら、{% data variables.projects.projects_v1_board %}への親チームのアクセスを変更しなければなりません。 +- 親チームへの{% data variables.projects.projects_v1_board %}へのアクセスを追加もしくは削除した場合、親チームのそれぞれの子チームも{% data variables.projects.projects_v1_board %}へのアクセスを受け取ったり失ったりします。 詳しい情報については[Team について](/articles/about-teams)を参照してください。 {% endwarning %} -## Giving a team access to a {% data variables.projects.projects_v1_board %} +## {% data variables.projects.projects_v1_board %}へのTeamのアクセスの付与 -You can give an entire team the same permission level to a {% data variables.projects.projects_v1_board %}. +Team全体に{% data variables.projects.projects_v1_board %}に対する同じ権限レベルを付与できます。 {% note %} -**Note:** {% data reusables.project-management.cascading-permissions %} For example, if an organization owner has given a team read permissions to a {% data variables.projects.projects_v1_board %}, and a {% data variables.projects.projects_v1_board %} admin gives one of the team members admin permissions to that board as an individual collaborator, that person would have admin permissions to the {% data variables.projects.projects_v1_board %}. For more information see, "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." +**ノート:** {% data reusables.project-management.cascading-permissions %} たとえば、Organization のオーナーが、ある{% data variables.projects.projects_v1_board %}に対する読み取り権限をチームに付与しており、{% data variables.projects.projects_v1_board %}の管理者がチームのメンバーいずれかに、個別のコラボレーターとしてそのボードに対する管理者権限を付与している場合、そのユーザは{% data variables.projects.projects_v1_board %}に対する管理者権限を持つことになります。 詳しい情報については「[Organizationの{% data variables.product.prodname_project_v1_caps %}の権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 {% endnote %} @@ -47,12 +47,12 @@ You can give an entire team the same permission level to a {% data variables.pro 9. チームを追加する場合は、[**Add a team: Select team**] をクリックします。 次に、ドロップダウン メニューからチームを選択するか、追加したいチームを検索します。 ![Organization のチームのリストが表示される [Add a team] ドロップダウン メニュー](/assets/images/help/projects/add-a-team.png) 10. チーム名の隣にあるドロップダウン メニューを使って、目的の権限レベルを [**Read**]、[**Write**]、[**Admin**] から選択します。 ![[Read]、[Write]、[Admin] のオプションがあるチームの権限](/assets/images/help/projects/org-project-team-choose-permissions.png) -## Configuring a team's access to a {% data variables.projects.projects_v1_board %} +## {% data variables.projects.projects_v1_board %}へのTeamのアクセスの設定 -If a team's access to a {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %} to update access to the child teams. +{% data variables.projects.projects_v1_board %}へのTeamのアクセスが親チームから継承されたものなら、子チームのアクセスを更新するには{% data variables.projects.projects_v1_board %}への親チームのアクセスを変更しなければなりません。 {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} 4. チームの会話の上にある {% octicon "project" aria-label="The Projects icon" %}[**Projects**] をクリックします。 ![チームの [Repositories] タブ](/assets/images/help/organizations/team-project-board-button.png) -5. To change permissions levels, to the right of the {% data variables.projects.projects_v1_board %} you want to update, use the drop-down. To remove a {% data variables.projects.projects_v1_board %}, click **{% octicon "trash" aria-label="The trash icon" %}**. ![チームからプロジェクトボードを削除する [Trash] ボタン](/assets/images/help/organizations/trash-button.png) +5. 権限レベルを変更するには、更新したい{% data variables.projects.projects_v1_board %}の右でドロップダウンを使ってください。 {% data variables.projects.projects_v1_board %}を削除するには**{% octicon "trash" aria-label="The trash icon" %}**をクリックしてください。 ![チームからプロジェクトボードを削除する [Trash] ボタン](/assets/images/help/organizations/trash-button.png) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index ba946be185..64d37366f8 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -60,123 +60,123 @@ Organizationレベルの設定の管理に加えて、Organizationのオーナ {% endnote %} {% endif %} -| リポジトリアクション | Read | Triage | Write | Maintain | Admin | -|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:-----:|:--------:|:-------------------------------------------------------------------:| -| リポジトリへの[個人](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)、[Team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)、[外部のコラボレータ](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)のアクセス管理 | | | | | **X** | -| 個人または Team の割り当てリポジトリからのプル | **X** | **X** | **X** | **X** | **X** | -| 個人または Team の割り当てリポジトリのフォーク | **X** | **X** | **X** | **X** | **X** | -| 自分のコメントの編集および削除 | **X** | **X** | **X** | **X** | **X** | -| Issue のオープン | **X** | **X** | **X** | **X** | **X** | -| 自分でオープンした Issue のクローズ | **X** | **X** | **X** | **X** | **X** | -| 自分でクローズした Issue を再オープン | **X** | **X** | **X** | **X** | **X** | -| 自分に割り当てられた Issue の取得 | **X** | **X** | **X** | **X** | **X** | -| Team の割り当てリポジトリのフォークからのプルリクエストの送信 | **X** | **X** | **X** | **X** | **X** | -| プルリクエストについてのレビューのサブミット | **X** | **X** | **X** | **X** | **X** | -| 公開済みリリースの表示 | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| [[GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)] の表示 | **X** | **X** | **X** | **X** | **X** +| リポジトリアクション | Read | Triage | Write | Maintain | Admin | +|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------:|:------:|:------:|:--------:|:--------------------------------------------------------------------:| +| リポジトリへの[個人](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)、[Team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)、[外部のコラボレータ](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)のアクセス管理 | | | | | **✔️** | +| 個人または Team の割り当てリポジトリからのプル | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 個人または Team の割り当てリポジトリのフォーク | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 自分のコメントの編集および削除 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Issue のオープン | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 自分でオープンした Issue のクローズ | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 自分でクローズした Issue を再オープン | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 自分に割り当てられた Issue の取得 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Team の割り当てリポジトリのフォークからのプルリクエストの送信 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| プルリクエストについてのレビューのサブミット | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 公開済みリリースの表示 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| [[GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)] の表示 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** {% endif %} -| パブリックリポジトリでのWikiの編集 | **X** | **X** | **X** | **X** | **X** | -| プライベートリポジトリのWikiの編集 | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| [悪用あるいはスパムの可能性があるコンテンツのレポート](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +| パブリックリポジトリでのWikiの編集 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| プライベートリポジトリのWikiの編集 | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| [悪用あるいはスパムの可能性があるコンテンツのレポート](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** {% endif %} -| ラベルの適用/却下 | | **X** | **X** | **X** | **X** | -| ラベルの作成、編集、削除 | | | **X** | **X** | **X** | -| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **X** | **X** | **X** | **X** | -| [プルリクエストの自動マージの有効化または無効化](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** | -| マイルストーンの適用 | | **X** | **X** | **X** | **X** | -| [重複した Issue とプルリクエスト](/articles/about-duplicate-issues-and-pull-requests)のマーク付け | | **X** | **X** | **X** | **X** | -| [プルリクエストのレビュー](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)の要求 | | **X** | **X** | **X** | **X** | -| [Pull Request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)のマージ | | | **X** | **X** | **X** | -| 個人または Team の割り当てリポジトリへのプッシュ (書き込み) | | | **X** | **X** | **X** | -| コミット、プルリクエスト、Issue についての他者によるコメントの編集と削除 | | | **X** | **X** | **X** | -| [他者によるコメントの非表示](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [会話のロック](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | -| Issue の移譲 (詳細は「[他のリポジトリへ Issue を移譲する](/articles/transferring-an-issue-to-another-repository)」を参照) | | | **X** | **X** | **X** | -| [リポジトリに指定されたコードオーナーとしてのアクション](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [プルリクエストのドラフトに、レビューの準備ができたことを示すマークを付ける](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| [プルリクエストをドラフトに変換する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| プルリクエストのマージ可能性に影響するレビューのサブミット | | | **X** | **X** | **X** | -| プルリクエストに[提案された変更を適用する](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) | | | **X** | **X** | **X** | -| [ステータスチェック](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)の作成 | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| [GitHub Actions ワークフロー](/actions/automating-your-workflow-with-github-actions/) の作成、編集、実行、再実行、キャンセル | | | **X** | **X** | **X** +| ラベルの適用/却下 | | **✔️** | **✔️** | **✔️** | **✔️** | +| ラベルの作成、編集、削除 | | | **✔️** | **✔️** | **✔️** | +| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **✔️** | **✔️** | **✔️** | **✔️** | +| [プルリクエストの自動マージの有効化または無効化](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **✔️** | **✔️** | **✔️** | +| マイルストーンの適用 | | **✔️** | **✔️** | **✔️** | **✔️** | +| [重複した Issue とプルリクエスト](/articles/about-duplicate-issues-and-pull-requests)のマーク付け | | **✔️** | **✔️** | **✔️** | **✔️** | +| [プルリクエストのレビュー](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)の要求 | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Pull Request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)のマージ | | | **✔️** | **✔️** | **✔️** | +| 個人または Team の割り当てリポジトリへのプッシュ (書き込み) | | | **✔️** | **✔️** | **✔️** | +| コミット、プルリクエスト、Issue についての他者によるコメントの編集と削除 | | | **✔️** | **✔️** | **✔️** | +| [他者によるコメントの非表示](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **✔️** | **✔️** | **✔️** | +| [会話のロック](/communities/moderating-comments-and-conversations/locking-conversations) | | | **✔️** | **✔️** | **✔️** | +| Issue の移譲 (詳細は「[他のリポジトリへ Issue を移譲する](/articles/transferring-an-issue-to-another-repository)」を参照) | | | **✔️** | **✔️** | **✔️** | +| [リポジトリに指定されたコードオーナーとしてのアクション](/articles/about-code-owners) | | | **✔️** | **✔️** | **✔️** | +| [プルリクエストのドラフトに、レビューの準備ができたことを示すマークを付ける](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | +| [プルリクエストをドラフトに変換する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | +| プルリクエストのマージ可能性に影響するレビューのサブミット | | | **✔️** | **✔️** | **✔️** | +| プルリクエストに[提案された変更を適用する](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) | | | **✔️** | **✔️** | **✔️** | +| [ステータスチェック](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)の作成 | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| [GitHub Actions ワークフロー](/actions/automating-your-workflow-with-github-actions/) の作成、編集、実行、再実行、キャンセル | | | **✔️** | **✔️** | **✔️** {% endif %} -| リリースの作成と編集 | | | **X** | **X** | **X** | -| ドラフトリリースの表示 | | | **X** | **X** | **X** | -| リポジトリの説明の編集 | | | | **X** | **X** |{% ifversion fpt or ghae or ghec %} -| [パッケージの表示とインストール](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [パッケージの公開](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [パッケージの削除および復元](/packages/learn-github-packages/deleting-and-restoring-a-package) | | | | | **X** |{% endif %} -| [Topics](/articles/classifying-your-repository-with-topics) の管理 | | | | **X** | **X** | -| Wiki の有効化および Wiki 編集者の制限 | | | | **X** | **X** | -| プロジェクトボードの有効化 | | | | **X** | **X** | -| [プルリクエストのマージ](/articles/configuring-pull-request-merges)の設定 | | | | **X** | **X** | -| [{% data variables.product.prodname_pages %} の公開ソース](/articles/configuring-a-publishing-source-for-github-pages)の設定 | | | | **X** | **X** | -| [ブランチ保護ルールの管理](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **X** | -| [保護されたブランチへのプッシュ](/articles/about-protected-branches) | | | | **X** | **X** | -| 保護されたブランチでのプルリクエストのマージ（レビューの承認がなくても） | | | | | **X** |{% ifversion fpt or ghes > 3.4 or ghae-issue-6337 or ghec %} -| [タグ保護ルール](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)にマッチするタグの作成 | | | | **X** | **X** | -| [タグ保護ルール](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)にマッチするタグの削除 | | | | | **X** +| リリースの作成と編集 | | | **✔️** | **✔️** | **✔️** | +| ドラフトリリースの表示 | | | **✔️** | **✔️** | **✔️** | +| リポジトリの説明の編集 | | | | **✔️** | **✔️** |{% ifversion fpt or ghae or ghec %} +| [パッケージの表示とインストール](/packages/publishing-and-managing-packages) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [パッケージの公開](/packages/publishing-and-managing-packages/publishing-a-package) | | | **✔️** | **✔️** | **✔️** | +| [パッケージの削除および復元](/packages/learn-github-packages/deleting-and-restoring-a-package) | | | | | **✔️** |{% endif %} +| [Topics](/articles/classifying-your-repository-with-topics) の管理 | | | | **✔️** | **✔️** | +| Wiki の有効化および Wiki 編集者の制限 | | | | **✔️** | **✔️** | +| プロジェクトボードの有効化 | | | | **✔️** | **✔️** | +| [プルリクエストのマージ](/articles/configuring-pull-request-merges)の設定 | | | | **✔️** | **✔️** | +| [{% data variables.product.prodname_pages %} の公開ソース](/articles/configuring-a-publishing-source-for-github-pages)の設定 | | | | **✔️** | **✔️** | +| [ブランチ保護ルールの管理](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **✔️** | +| [保護されたブランチへのプッシュ](/articles/about-protected-branches) | | | | **✔️** | **✔️** | +| 保護されたブランチでのプルリクエストのマージ（レビューの承認がなくても） | | | | | **✔️** |{% ifversion fpt or ghes > 3.4 or ghae-issue-6337 or ghec %} +| [タグ保護ルール](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)にマッチするタグの作成 | | | | **✔️** | **✔️** | +| [タグ保護ルール](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)にマッチするタグの削除 | | | | | **✔️** {% endif %} -| [リポジトリソーシャルカードの作成と編集](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt or ghec %} -| [リポジトリでのインタラクション](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)を制限する | | | | **X** | **X** +| [リポジトリソーシャルカードの作成と編集](/articles/customizing-your-repositorys-social-media-preview) | | | | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| [リポジトリでのインタラクション](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)を制限する | | | | **✔️** | **✔️** {% endif %} -| Issue の削除 (「[Issue を削除する](/articles/deleting-an-issue)」を参照) | | | | | **X** | -| [リポジトリのコードオーナーの定義](/articles/about-code-owners) | | | | | **X** | -| リポジトリを Team に追加する (詳細は「[Organization リポジトリへの Team のアクセスを管理する](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)」を参照) | | | | | **X** | -| [外部のコラボレータのリポジトリへのアクセスの管理](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [リポジトリの可視性の変更](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| リポジトリのテンプレート化 (「[テンプレートリポジトリを作成する](/articles/creating-a-template-repository)」を参照) | | | | | **X** | -| リポジトリ設定の変更 | | | | | **X** | -| Team およびコラボレータのリポジトリへのアクセス管理 | | | | | **X** | -| リポジトリのデフォルトブランチ編集 | | | | | **X** | -| リポジトリのデフォルトブランチの名前を変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照） | | | | | **X** | -| リポジトリのデフォルトブランチを変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照） | | | **X** | **X** | **X** | -| Webhookおよびデプロイキーの管理 | | | | | **X** |{% ifversion fpt or ghec %} -| [プライベートリポジトリ用のデータ利用設定を管理する](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository) | | | | | **X** +| Issue の削除 (「[Issue を削除する](/articles/deleting-an-issue)」を参照) | | | | | **✔️** | +| [リポジトリのコードオーナーの定義](/articles/about-code-owners) | | | | | **✔️** | +| リポジトリを Team に追加する (詳細は「[Organization リポジトリへの Team のアクセスを管理する](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)」を参照) | | | | | **✔️** | +| [外部のコラボレータのリポジトリへのアクセスの管理](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **✔️** | +| [リポジトリの可視性の変更](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **✔️** | +| リポジトリのテンプレート化 (「[テンプレートリポジトリを作成する](/articles/creating-a-template-repository)」を参照) | | | | | **✔️** | +| リポジトリ設定の変更 | | | | | **✔️** | +| Team およびコラボレータのリポジトリへのアクセス管理 | | | | | **✔️** | +| リポジトリのデフォルトブランチ編集 | | | | | **✔️** | +| リポジトリのデフォルトブランチの名前を変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照） | | | | | **✔️** | +| リポジトリのデフォルトブランチを変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照） | | | **✔️** | **✔️** | **✔️** | +| Webhookおよびデプロイキーの管理 | | | | | **✔️** |{% ifversion fpt or ghec %} +| [プライベートリポジトリ用のデータ利用設定を管理する](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository) | | | | | **✔️** {% endif %} -| [リポジトリのフォークポリシーを管理する](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [リポジトリの Organization への移譲](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [リポジトリの削除または Organization 外への移譲](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [リポジトリのアーカイブ](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt or ghec %} -| スポンサーボタンの表示 (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照) | | | | | **X** +| [リポジトリのフォークポリシーを管理する](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **✔️** | +| [リポジトリの Organization への移譲](/articles/restricting-repository-creation-in-your-organization) | | | | | **✔️** | +| [リポジトリの削除または Organization 外への移譲](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **✔️** | +| [リポジトリのアーカイブ](/articles/about-archiving-repositories) | | | | | **✔️** |{% ifversion fpt or ghec %} +| スポンサーボタンの表示 (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照) | | | | | **✔️** {% endif %} -| JiraやZendeskなどの外部リソースに対する自動リンク参照の作成 (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。 | | | | | **X** |{% ifversion discussions %} -| リポジトリの [{% data variables.product.prodname_discussions %} の有効化](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) | | | | **X** | **X** | -| {% data variables.product.prodname_discussions %} の[カテゴリの作成および編集](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) | | | | **X** | **X** | -| [ディスカッションを別のカテゴリに移動する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| 新しいリポジトリに[ディスカッションを転送する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [ピン止めされたディスカッションを管理する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [Issue をまとめてディスカッションに変換する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [ディスカッションのロックとロック解除](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Issue を個別にディスカッションに変換する](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [新しいディスカッションを作成し、既存のディスカッションにコメントする](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | -| [ディスカッションの削除](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **X** | | **X** | **X** |{% endif %}{% ifversion fpt or ghec %} -| [codespaces](/codespaces/about-codespaces)の作成 | | | **X** | **X** | **X** +| JiraやZendeskなどの外部リソースに対する自動リンク参照の作成 (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。 | | | | | **✔️** |{% ifversion discussions %} +| リポジトリの [{% data variables.product.prodname_discussions %} の有効化](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) | | | | **✔️** | **✔️** | +| {% data variables.product.prodname_discussions %} の[カテゴリの作成および編集](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) | | | | **✔️** | **✔️** | +| [ディスカッションを別のカテゴリに移動する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| 新しいリポジトリに[ディスカッションを転送する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [ピン止めされたディスカッションを管理する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [Issue をまとめてディスカッションに変換する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [ディスカッションのロックとロック解除](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Issue を個別にディスカッションに変換する](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | +| [新しいディスカッションを作成し、既存のディスカッションにコメントする](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [ディスカッションの削除](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **✔️** | | **✔️** | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| [codespaces](/codespaces/about-codespaces)の作成 | | | **✔️** | **✔️** | **✔️** {% endif %} ### セキュリティ機能のためのアクセス要件 このセクションでは、{% data variables.product.prodname_advanced_security %}の機能のようなセキュリティ機能に必要なアクセス権を知ることができます。 -| リポジトリアクション | Read | Triage | Write | Maintain | Admin | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------:| -| リポジトリでの[安全ではない依存関係に対する{% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)を受信 | | | | | **X** | -| [{% data variables.product.prodname_dependabot_alerts %} を閉じる](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% ifversion ghes or ghae or ghec %} +| リポジトリアクション | Read | Triage | Write | Maintain | Admin | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------:|:------:|:-------------------------------------------------------:|:-------------------------------------------------------:|:--------------------------------------------------------------------------------------------------:| +| リポジトリでの[安全ではない依存関係に対する{% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)を受信 | | | | | **✔️** | +| [{% data variables.product.prodname_dependabot_alerts %} を閉じる](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **✔️** |{% ifversion ghes or ghae or ghec %} | -| [セキュリティアラートを受信する追加のユーザまたはTeamの指定](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} -| [セキュリティアドバイザリ](/code-security/security-advisories/about-github-security-advisories)の作成 | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [セキュリティアラートを受信する追加のユーザまたはTeamの指定](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| [セキュリティアドバイザリ](/code-security/security-advisories/about-github-security-advisories)の作成 | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} | -| {% data variables.product.prodname_GH_advanced_security %}の機能へのアクセス管理（「[Organizationのセキュリティと分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」参照） | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} +| {% data variables.product.prodname_GH_advanced_security %}の機能へのアクセス管理（「[Organizationのセキュリティと分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」参照） | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} | -| プライベートリポジトリの[依存関係グラフの有効化](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} -| [依存関係のレビューを表示する](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** +| プライベートリポジトリの[依存関係グラフの有効化](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [依存関係のレビューを表示する](/code-security/supply-chain-security/about-dependency-review) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** {% endif %} -| [プルリクエストの {% data variables.product.prodname_code_scanning %} アラートを表示する](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | -| [{% data variables.product.prodname_code_scanning %} アラートを一覧表示、却下、削除します](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | -| [リポジトリの {% data variables.product.prodname_secret_scanning %} アラートを表示する](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} +| [プルリクエストの {% data variables.product.prodname_code_scanning %} アラートを表示する](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [{% data variables.product.prodname_code_scanning %} アラートを一覧表示、却下、削除します](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **✔️** | **✔️** | **✔️** | +| [リポジトリの {% data variables.product.prodname_secret_scanning %} アラートを表示する](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% ifversion ghes or ghae or ghec %} | -| [{% data variables.product.prodname_secret_scanning %} アラートを解決、取り消し、再オープンする](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} -| リポジトリで [{% data variables.product.prodname_secret_scanning %} アラートを受信する追加の人または Team を指定する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** +| [{% data variables.product.prodname_secret_scanning %} アラートを解決、取り消し、再オープンする](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| リポジトリで [{% data variables.product.prodname_secret_scanning %} アラートを受信する追加の人または Team を指定する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **✔️** {% endif %} [1] リポジトリの作者とメンテナは、自分のコミットのアラート情報のみを表示できます。 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md index 64a9a3cff9..5274dffcd6 100644 --- a/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md @@ -1,5 +1,5 @@ --- -title: Allowing project visibility changes in your organization +title: Organizationでのプロジェクトの可視性の変更の許可 intro: Organization owners can allow members with admin permissions to adjust the visibility of projects in their organization. versions: feature: projects-v2 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md index bc4e39f1ac..276b444e49 100644 --- a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md @@ -17,7 +17,7 @@ After you disable insights for projects in your organization, it won't be possib {% data reusables.profile.org_settings %} 1. In the sidebar, click **{% octicon "sliders" aria-label="The sliders icon" %} Features**. ![Screenshot showing features menu item](/assets/images/help/projects-v2/features-org-menu.png) 1. Under "Insights", deselect **Enable Insights for the organization**. ![Screenshot showing Enable Insights for the organization checkbox](/assets/images/help/projects-v2/disable-insights-checkbox.png) -1. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/disable-insights-save.png) +1. [**Save**] をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/disable-insights-save.png) ## 参考リンク diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index 8483bb41ab..9dde67b4b6 100644 --- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -12,14 +12,12 @@ topics: shortTitle: SAML SSOを使うIAM --- -{% data reusables.enterprise-accounts.emu-saml-note %} +{% data reusables.saml.ghec-only %} ## SAML SSO について {% data reusables.saml.dotcom-saml-explanation %} -{% data reusables.saml.ghec-only %} - {% data reusables.saml.saml-accounts %} Organization のオーナーは、個々の Organization に SAML SSO を適用できます。または、Enterprise のオーナーは、Enterprise アカウント内のすべての Organization に SAML SSO を適用できます。 詳しい情報については、「[Enterprise 向けのSAML シングルサインオンを設定する](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)」を参照してください。 diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md index 765d90a90f..d270178440 100644 --- a/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -126,6 +126,7 @@ In addition, your use of {% data variables.product.prodname_pages %} is subject {% ifversion fpt or ghec %} - {% data variables.product.prodname_pages %} sites have a *soft* bandwidth limit of 100 GB per month. - {% data variables.product.prodname_pages %} sites have a *soft* limit of 10 builds per hour.{% ifversion pages-custom-workflow %} This limit does not apply if you build and publish your site with a custom {% data variables.product.prodname_actions %} workflow {% endif %} + - In order to provide consistent quality of service for all {% data variables.product.prodname_pages %} sites, rate limits may apply. These rate limits are not intended to interfere with legitimate uses of {% data variables.product.prodname_pages %}. If your request triggers rate limiting, you will receive an appropriate response with an HTTP status code of `429`, along with an informative HTML body. If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from {% data variables.contact.contact_support %} suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other {% data variables.product.prodname_dotcom %} features such as releases, or moving to a different hosting service that might better fit your needs. diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md index 2c5cf2886c..1a2fea66fe 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -25,6 +25,7 @@ You can create a branch in different ways on {% data variables.product.product_n {% endnote %} +{% ifversion create-branch-from-overview %} ### Creating a branch via the branches overview {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-branches %} @@ -32,16 +33,19 @@ You can create a branch in different ways on {% data variables.product.product_n 2. In the dialog box, enter the branch name and optionally change the branch source. If the repository is a fork, you also have the option to select the upstream repository as the branch source. ![Screenshot of branch creation modal for a fork with branch source emphasized](/assets/images/help/branches/branch-creation-popup-branch-source.png) 3. Click **Create branch**. ![Screenshot of branch creation modal with create branch button emphasized](/assets/images/help/branches/branch-creation-popup-button.png) +{% endif %} ### Creating a branch using the branch dropdown {% data reusables.repositories.navigate-to-repo %} 1. Optionally, if you want to create the new branch from a branch other than the default branch of the repository, click {% octicon "git-branch" aria-label="The branch icon" %} **Branches** then choose another branch. ![概要ページのブランチリンク](/assets/images/help/branches/branches-overview-link.png) 1. ブランチセレクタメニューをクリックします。 ![ブランチセレクタメニュー](/assets/images/help/branch/branch-selection-dropdown.png) 1. 新しいブランチに、一意の名前を入力して、[**Create branch**] を選択します。 ![ブランチ作成のテキストボックス](/assets/images/help/branch/branch-creation-text-box.png) + {% ifversion fpt or ghec or ghes > 3.4 %} ### Issueのためのブランチの作成 直接Issueのページから作業のためのブランチを作成し、すぐに作業を開始できます。 For more information, see "[Creating a branch to work on an issue](/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue)". {% endif %} + ## ブランチの削除 {% data reusables.pull_requests.automatically-delete-branches %} diff --git a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md index 94eb059bfb..a719f4b0cb 100644 --- a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md @@ -226,7 +226,7 @@ REST API を介して `node_id` を検索し、それらを GraphQL 操作で使 ## HTTP メソッド -可能な場合、{% data variables.product.product_name %} REST APIはそれぞれのアクションに対して適切なHTTPメソッドを使うように努めます。 +可能な場合、{% data variables.product.product_name %} REST APIはそれぞれのアクションに対して適切なHTTPメソッドを使うように努めます。 Note that HTTP verbs are case-sensitive. | メソッド | 説明 | | -------- | ----------------------------------------------------------------------------------------------------------------------------- | diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md b/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md index 750c7d68df..f269b7fbf7 100644 --- a/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md @@ -91,7 +91,7 @@ With the `in` qualifier you can restrict your search to the repository name, rep | 修飾子 | サンプル | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) は、Star がちょうど 500 のリポジトリにマッチします。 | -| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) は、1000 KB 未満で、Star が 10 から 20 のリポジトリにマッチします。 | +| | [**stars:10..20 size:<1000**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB. | | | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) は、PHP 形式のフォークされたリポジトリを含め Star が 500 以上のリポジトリにマッチします。 | ## リポジトリの作成時期や最終更新時期で検索 diff --git a/translations/ja-JP/data/features/create-branch-from-overview.yml b/translations/ja-JP/data/features/create-branch-from-overview.yml new file mode 100644 index 0000000000..a51e624c41 --- /dev/null +++ b/translations/ja-JP/data/features/create-branch-from-overview.yml @@ -0,0 +1,5 @@ +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.7' + ghae: 'issue-6670' diff --git a/translations/ja-JP/data/features/security-overview-displayed-alerts.yml b/translations/ja-JP/data/features/security-overview-displayed-alerts.yml new file mode 100644 index 0000000000..da84d07e41 --- /dev/null +++ b/translations/ja-JP/data/features/security-overview-displayed-alerts.yml @@ -0,0 +1,6 @@ +#Reference: #7114. +#Documentation for security overview availability to all enterprise accounts. +versions: + ghec: '*' + ghes: '>=3.7' + ghae: 'issue-7114' diff --git a/translations/ja-JP/data/features/totp-and-mobile-sudo-challenge.yml b/translations/ja-JP/data/features/totp-and-mobile-sudo-challenge.yml new file mode 100644 index 0000000000..0eae9cda9c --- /dev/null +++ b/translations/ja-JP/data/features/totp-and-mobile-sudo-challenge.yml @@ -0,0 +1,5 @@ +#TOTP and mobile challenge for sudo mode prompt. +versions: + fpt: '*' + ghec: '*' + ghes: '>= 3.7' diff --git a/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml b/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml index 10abd35353..fc8477114a 100644 --- a/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml +++ b/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml @@ -154,6 +154,13 @@ upcoming_changes: date: '2022-10-01T00:00:00+00:00' criticality: 破壊的 owner: lukewar + - + location: ProjectNextFieldType.TASKS + description: '`TASKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + reason: '`ProjectNext`は、より多機能な`ProjectV2`に置き換えられて非推奨になりました。' + date: '2022-10-01T00:00:00+00:00' + criticality: 破壊的 + owner: lukewar - location: ProjectNextFieldType.TEXT description: '`TEXT`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' @@ -168,13 +175,6 @@ upcoming_changes: date: '2022-10-01T00:00:00+00:00' criticality: 破壊的 owner: lukewar - - - location: ProjectNextFieldType.TRACKS - description: '`TRACKS`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' - reason: '`ProjectNext`は、より多機能な`ProjectV2`に置き換えられて非推奨になりました。' - date: '2022-10-01T00:00:00+00:00' - criticality: 破壊的 - owner: lukewar - location: RemovePullRequestFromMergeQueueInput.branch description: '`branch`は削除されます。' diff --git a/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml b/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml index f7cdd42018..7b4b915eef 100644 --- a/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml +++ b/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml @@ -574,6 +574,13 @@ upcoming_changes: date: '2022-10-01T00:00:00+00:00' criticality: 破壊的 owner: lukewar + - + location: ProjectNextFieldType.TASKS + description: '`TASKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + reason: '`ProjectNext`は、より多機能な`ProjectV2`に置き換えられて非推奨になりました。' + date: '2022-10-01T00:00:00+00:00' + criticality: 破壊的 + owner: lukewar - location: ProjectNextFieldType.TEXT description: '`TEXT`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' @@ -588,13 +595,6 @@ upcoming_changes: date: '2022-10-01T00:00:00+00:00' criticality: 破壊的 owner: lukewar - - - location: ProjectNextFieldType.TRACKS - description: '`TRACKS`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' - reason: '`ProjectNext`は、より多機能な`ProjectV2`に置き換えられて非推奨になりました。' - date: '2022-10-01T00:00:00+00:00' - criticality: 破壊的 - owner: lukewar - location: ProjectNextItem.content description: '`content`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' diff --git a/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml b/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml index f7cdd42018..7b4b915eef 100644 --- a/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml @@ -574,6 +574,13 @@ upcoming_changes: date: '2022-10-01T00:00:00+00:00' criticality: 破壊的 owner: lukewar + - + location: ProjectNextFieldType.TASKS + description: '`TASKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + reason: '`ProjectNext`は、より多機能な`ProjectV2`に置き換えられて非推奨になりました。' + date: '2022-10-01T00:00:00+00:00' + criticality: 破壊的 + owner: lukewar - location: ProjectNextFieldType.TEXT description: '`TEXT`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' @@ -588,13 +595,6 @@ upcoming_changes: date: '2022-10-01T00:00:00+00:00' criticality: 破壊的 owner: lukewar - - - location: ProjectNextFieldType.TRACKS - description: '`TRACKS`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' - reason: '`ProjectNext`は、より多機能な`ProjectV2`に置き換えられて非推奨になりました。' - date: '2022-10-01T00:00:00+00:00' - criticality: 破壊的 - owner: lukewar - location: ProjectNextItem.content description: '`content`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' diff --git a/translations/ja-JP/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md b/translations/ja-JP/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md index b4d7a50a1d..aa6186a5bb 100644 --- a/translations/ja-JP/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md +++ b/translations/ja-JP/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md @@ -6,7 +6,7 @@ ### {% data variables.product.prodname_dotcom %}ホストランナーの選択 -{% data variables.product.prodname_dotcom %}ホストランナーを使う場合、それぞれのジョブは`runs-on`で指定された仮想環境の新しいインスタンスで実行されます。 +If you use a {% data variables.product.prodname_dotcom %}-hosted runner, each job runs in a fresh instance of a runner image specified by `runs-on`. 利用可能な{% data variables.product.prodname_dotcom %}ホストランナーの種類は以下のとおりです。 @@ -18,7 +18,7 @@ runs-on: ubuntu-latest ``` -詳しい情報については「[{% data variables.product.prodname_dotcom %}ホストランナーの仮想環境](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)」を参照してください。 +詳しい情報については「[{% data variables.product.prodname_dotcom %}ホストランナーについて](/actions/using-github-hosted-runners/about-github-hosted-runners)」を参照してください。 {% endif %} {% ifversion fpt or ghec or ghes %} diff --git a/translations/ja-JP/data/reusables/actions/macos-runner-preview.md b/translations/ja-JP/data/reusables/actions/macos-runner-preview.md index b96f447329..c9b93aecbe 100644 --- a/translations/ja-JP/data/reusables/actions/macos-runner-preview.md +++ b/translations/ja-JP/data/reusables/actions/macos-runner-preview.md @@ -1 +1 @@ -macos-latestのYAMLワークフローのラベルは、現在macOS 10.15の仮想環境を使用します。 +The macos-latest YAML workflow label currently uses the macOS 10.15 runner image. diff --git a/translations/ja-JP/data/reusables/actions/pure-javascript.md b/translations/ja-JP/data/reusables/actions/pure-javascript.md index db4eec7753..933fe00c03 100644 --- a/translations/ja-JP/data/reusables/actions/pure-javascript.md +++ b/translations/ja-JP/data/reusables/actions/pure-javascript.md @@ -1 +1 @@ -JavaScriptのアクションがGitHubがホストするすべてのランナー（Ubuntu、Windows、macOS）と互換性があることを保証するためには、作成するパッケージ化されたJacScriptのコードは純粋なJavaScriptであり、他のバイナリに依存していてはなりません。 JavaScriptのアクションはランナー上で直接実行され、仮想環境内にすでに存在するバイナリを利用します。 +JavaScriptのアクションがGitHubがホストするすべてのランナー（Ubuntu、Windows、macOS）と互換性があることを保証するためには、作成するパッケージ化されたJacScriptのコードは純粋なJavaScriptであり、他のバイナリに依存していてはなりません。 JavaScript actions run directly on the runner and use binaries that already exist in the runner image. diff --git a/translations/ja-JP/data/reusables/actions/supported-github-runners.md b/translations/ja-JP/data/reusables/actions/supported-github-runners.md index 68b601bbc8..8f3ec2e695 100644 --- a/translations/ja-JP/data/reusables/actions/supported-github-runners.md +++ b/translations/ja-JP/data/reusables/actions/supported-github-runners.md @@ -1,7 +1,7 @@
Entorno virtualRunner image Etiqueta de flujo de trabajo YAML Notas
-Ubuntu 22.04 se encuentra actualmente en beta público.
-Ubuntu 18.04 +Ubuntu 18.04 [deprecated] ubuntu-18.04 +Migrate to ubuntu-20.04 or ubuntu-22.04. Para obtener más información, consulta esta publicación del blog de GitHub.
- + @@ -92,7 +92,7 @@ macOS Catalina 10.15 [deprecated] {% note %} -**ノート:** `-latest`の仮想環境は、{% data variables.product.prodname_dotcom %}が提供している最新の安定版イメージであり、オペレーティングシステムのベンダーから提供されているオペレーティングシステムの最新バージョンではないことがあります。 +**Note:** The `-latest` runner images are the latest stable images that {% data variables.product.prodname_dotcom %} provides, and might not be the most recent version of the operating system available from the operating system vendor. {% endnote %} diff --git a/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md index 6ad33181dd..fa6ffee006 100644 --- a/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md +++ b/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md @@ -19,7 +19,11 @@ ![新しい {% data variables.product.prodname_codespaces %} を作成するためのブランチを検索する](/assets/images/help/codespaces/choose-branch-vscode.png) -5. 使用したいマシンタイプをクリックしてください。 +5. If prompted to choose a dev container configuration file, choose a file from the list. + + ![Choosing a dev container configuration file for {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-dev-container-vscode.png) + +6. 使用したいマシンタイプをクリックしてください。 ![新しい {% data variables.product.prodname_codespaces %} のインスタンスタイプ](/assets/images/help/codespaces/choose-sku-vscode.png) diff --git a/translations/ja-JP/data/reusables/gated-features/advanced-security.md b/translations/ja-JP/data/reusables/gated-features/advanced-security.md deleted file mode 100644 index a8a075f2fe..0000000000 --- a/translations/ja-JP/data/reusables/gated-features/advanced-security.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_GH_advanced_security %} is a set of security features designed to make enterprise code more secure. It is available for {% data variables.product.prodname_ghe_server %} 3.0 or higher, {% data variables.product.prodname_ghe_cloud %}, and open source repositories. To learn more about the features included in {% data variables.product.prodname_GH_advanced_security %}, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)." diff --git a/translations/ja-JP/data/reusables/gated-features/ghas.md b/translations/ja-JP/data/reusables/gated-features/ghas.md index 0f74920694..b6362ec2f9 100644 --- a/translations/ja-JP/data/reusables/gated-features/ghas.md +++ b/translations/ja-JP/data/reusables/gated-features/ghas.md @@ -1 +1 @@ -{% data variables.product.prodname_GH_advanced_security %} is available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %} 3.0 or higher.{% ifversion fpt or ghec %} {% data variables.product.prodname_GH_advanced_security %} is also included in all public repositories on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."{% else %} For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.{% endif %} +{% data variables.product.prodname_GH_advanced_security %} is available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}.{% ifversion fpt or ghec %} Some features of {% data variables.product.prodname_GH_advanced_security %} are also available for public repositories on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."{% else %} For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.{% endif %} diff --git a/translations/ja-JP/data/reusables/gated-features/security-overview.md b/translations/ja-JP/data/reusables/gated-features/security-overview.md index d3f9f4b3ce..7a4f00d780 100644 --- a/translations/ja-JP/data/reusables/gated-features/security-overview.md +++ b/translations/ja-JP/data/reusables/gated-features/security-overview.md @@ -1,6 +1,9 @@ -{% ifversion ghae %} -{% data variables.product.prodname_GH_advanced_security %}のライセンスを持っているなら、Organizationのセキュリティの概要が利用できます。これは、ベータリリースの間は無料です。 {% data reusables.advanced-security.more-info-ghas %} -{% elsif ghec or ghes %} +{% ifversion fpt %} +The security overview is available for organizations that use {% data variables.product.prodname_enterprise %}. 詳しい情報については「[GitHubの製品](/articles/githubs-products)」を参照してください。 +{% elsif security-overview-displayed-alerts %} +All organizations and enterprises have a security overview. If you use {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghae %}, which is free during the beta release,{% endif %} you will see additional information. {% data reusables.advanced-security.more-info-ghas %} +{% elsif ghes < 3.7 %} The security overview for your organization is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %} -{% elsif fpt %} -The security overview is available for organizations that use {% data variables.product.prodname_enterprise %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. 詳しい情報については「[{% data variables.product.prodname_GH_advanced_security %}について](/get-started/learning-about-github/about-github-advanced-security)」を参照してください。 {% endif %} +{% elsif ghae %} +A security overview for your enterprise and for organizations is available if you use {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release. {% data reusables.advanced-security.more-info-ghas %} +{% endif %} diff --git a/translations/ja-JP/data/reusables/projects/add-draft-issue.md b/translations/ja-JP/data/reusables/projects/add-draft-issue.md index ce0fd22442..1ab213586c 100644 --- a/translations/ja-JP/data/reusables/projects/add-draft-issue.md +++ b/translations/ja-JP/data/reusables/projects/add-draft-issue.md @@ -1,3 +1,3 @@ {% data reusables.projects.add-item-bottom-row %} -1. アイデアを入力し、**Enter**を押してください。 ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-draft-issue.png) +1. アイデアを入力し、**Enter**を押してください。 ![IssueのURLを貼り付けてプロジェクトに追加しているスクリーンショット](/assets/images/help/projects-v2/add-draft-issue.png) 1. 本文のテキストを追加するには、ドラフトIssueのタイトルをクリックしてください。 表示されるMarkdownの入力ボックスに、ドラフトIssueの本文のテキストを入力し、**Save（保存）**をクリックしてください。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/projects/add-item-via-paste.md b/translations/ja-JP/data/reusables/projects/add-item-via-paste.md index f0ad9645a0..ddae60160c 100644 --- a/translations/ja-JP/data/reusables/projects/add-item-via-paste.md +++ b/translations/ja-JP/data/reusables/projects/add-item-via-paste.md @@ -1,3 +1,3 @@ {% data reusables.projects.add-item-bottom-row %} -1. Paste the URL of the issue or pull request. ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/paste-url-to-add.png) +1. Paste the URL of the issue or pull request. ![IssueのURLを貼り付けてプロジェクトに追加しているスクリーンショット](/assets/images/help/projects-v2/paste-url-to-add.png) 3. To add the issue or pull request, press Return. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md b/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md index 24ad34d005..3a854d7655 100644 --- a/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md +++ b/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md @@ -1,7 +1,7 @@ 1. プロジェクトにアクセスします。 -1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) -1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**. ![Screenshot showing the 'Workflows' menu item](/assets/images/help/projects-v2/workflows-menu-item.png) -1. Under **Default workflows**, click on the workflow that you want to edit. ![Screenshot showing default workflows](/assets/images/help/projects-v2/default-workflows.png) -1. If the workflow can apply to both issues and pull requests, next to **When**, check the item type(s) that you want to act on. ![Screenshot showing the "when" configuration for a workflow](/assets/images/help/projects-v2/workflow-when.png) -1. Next to **Set**, choose the value that you want to set the status to. ![Screenshot showing the "set" configuration for a workflow](/assets/images/help/projects-v2/workflow-set.png) -1. If the workflow is disabled, click the toggle next to **Disabled** to enable the workflow. ![Screenshot showing the "enable" control for a workflow](/assets/images/help/projects-v2/workflow-enable.png) +1. 右上で{% octicon "kebab-horizontal" aria-label="The menu icon" %}をクリックしてメニューを開いてください。 ![メニューアイコンを表示しているスクリーンショット](/assets/images/help/projects-v2/open-menu.png) +1. メニューで{% octicon "workflow" aria-label="The workflow icon" %} **Workflows（ワークフロー）**をクリックしてください。 !['Workflows'メニューアイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/workflows-menu-item.png) +1. Under **Default workflows**, click on the workflow that you want to edit. ![デフォルトのワークフローを表示しているスクリーンショット](/assets/images/help/projects-v2/default-workflows.png) +1. If the workflow can apply to both issues and pull requests, next to **When**, check the item type(s) that you want to act on. ![ワークフローの"when"設定を表示しているスクリーンショット](/assets/images/help/projects-v2/workflow-when.png) +1. Next to **Set**, choose the value that you want to set the status to. ![ワークフローの"set"設定を表示しているスクリーンショット](/assets/images/help/projects-v2/workflow-set.png) +1. If the workflow is disabled, click the toggle next to **Disabled** to enable the workflow. ![ワークフローの"enable"コントロールを表示しているスクリーンショット](/assets/images/help/projects-v2/workflow-enable.png) diff --git a/translations/ja-JP/data/reusables/projects/project-settings.md b/translations/ja-JP/data/reusables/projects/project-settings.md index 77fff8c531..68ebdfd368 100644 --- a/translations/ja-JP/data/reusables/projects/project-settings.md +++ b/translations/ja-JP/data/reusables/projects/project-settings.md @@ -1,3 +1,3 @@ 1. プロジェクトにアクセスします。 -1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) +1. 右上で{% octicon "kebab-horizontal" aria-label="The menu icon" %}をクリックしてメニューを開いてください。 ![メニューアイコンを表示しているスクリーンショット](/assets/images/help/projects-v2/open-menu.png) 2. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings. ![Screenshot showing the 'Settings' menu item](/assets/images/help/projects-v2/settings-menu-item.png) diff --git a/translations/ja-JP/data/reusables/projects/reopen-a-project.md b/translations/ja-JP/data/reusables/projects/reopen-a-project.md index 9be346cda1..bef6c7ee87 100644 --- a/translations/ja-JP/data/reusables/projects/reopen-a-project.md +++ b/translations/ja-JP/data/reusables/projects/reopen-a-project.md @@ -1,6 +1,6 @@ 1. Click the **Projects** tab. ![プロジェクトのクローズボタンが表示されているスクリーンショット](/assets/images/help/issues/projects-profile-tab.png) 1. To show closed projects, click **Closed**. ![プロジェクトのクローズボタンが表示されているスクリーンショット](/assets/images/help/issues/closed-projects-tab.png) 1. Click the project you want to reopen. -1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) +1. 右上で{% octicon "kebab-horizontal" aria-label="The menu icon" %}をクリックしてメニューを開いてください。 ![メニューアイコンを表示しているスクリーンショット](/assets/images/help/projects-v2/open-menu.png) 1. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings. ![Screenshot showing the 'Settings' menu item](/assets/images/help/projects-v2/settings-menu-item.png) 1. At the bottom of the page, click **Re-open project**. ![Screenshot showing project re-open button](/assets/images/help/issues/reopen-project-button.png) diff --git a/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md b/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md index 1193514f50..d8413a8725 100644 --- a/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md +++ b/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -SAML single sign-on (SSO) gives organization owners and enterprise owners using {% data variables.product.product_name %} a way to control and secure access to organization resources like repositories, issues, and pull requests. +SAML single sign-on (SSO) gives organization owners and enterprise owners using {% data variables.product.product_name %} a way to control and secure access to organization resources like repositories, issues, and pull requests. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/saml/outside-collaborators-exemption.md b/translations/ja-JP/data/reusables/saml/outside-collaborators-exemption.md index ffab0f818a..cc15ec0c4e 100644 --- a/translations/ja-JP/data/reusables/saml/outside-collaborators-exemption.md +++ b/translations/ja-JP/data/reusables/saml/outside-collaborators-exemption.md @@ -1,5 +1,8 @@ {% note %} -**Note:** 外部のコラボレータは、SAML SSOを使っているOrganization内のリソースにアクセスするために、IdPでの認証を受ける必要はありません。 For more information on outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)." +**ノート:** + +- SAML authentication is not required for organization members to perform read operations such as viewing, cloning, and forking of public resources. +- SAML authentication is not required for outside collaborators. 外部コラボレータに関する詳しい情報については「[Organization内のロール](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)」を参照してください。 {% endnote %} diff --git a/translations/ja-JP/data/reusables/saml/saml-accounts.md b/translations/ja-JP/data/reusables/saml/saml-accounts.md index cc2788744f..7a9dbdd87a 100644 --- a/translations/ja-JP/data/reusables/saml/saml-accounts.md +++ b/translations/ja-JP/data/reusables/saml/saml-accounts.md @@ -1,7 +1,7 @@ -If you configure SAML SSO, members of your organization will continue to log into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}. When a member accesses non-public resources within your organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} redirects the member to your IdP to authenticate. 認証に成功すると、IdP はメンバーを {% data variables.product.prodname_dotcom %} にリダイレクトして戻し、そこでメンバーは Organization のリソースにアクセスできます。 +If you configure SAML SSO, members of your organization will continue to sign into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}. When a member accesses non-public resources within your organization, {% data variables.product.prodname_dotcom %} redirects the member to your IdP to authenticate. After successful authentication, your IdP redirects the member back to {% data variables.product.prodname_dotcom %}. 詳しい情報については「[SAML シングルサインオンでの認証について](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)」を参照してください。 {% note %} -**Note:** Organization members can perform read operations such as viewing, cloning, and forking on public resources owned by your organization even without a valid SAML session. +**Note:** SAML SSO does not replace the normal sign-in process for {% data variables.product.prodname_dotcom %}. Unless you use {% data variables.product.prodname_emus %}, members will continue to sign into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}, and each personal account will be linked to an external identity in your IdP. -{% endnote %} +{% endnote %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/security-overview/information-varies-GHAS.md b/translations/ja-JP/data/reusables/security-overview/information-varies-GHAS.md new file mode 100644 index 0000000000..7d642c7fda --- /dev/null +++ b/translations/ja-JP/data/reusables/security-overview/information-varies-GHAS.md @@ -0,0 +1,3 @@ +{% ifversion security-overview-displayed-alerts %} +The information shown in the security overview will vary according to your access to repositories, and on whether {% data variables.product.prodname_GH_advanced_security %} is used by those repositories. +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/user-settings/sudo-mode-popup.md b/translations/ja-JP/data/reusables/user-settings/sudo-mode-popup.md index f76378972a..ec184765fe 100644 --- a/translations/ja-JP/data/reusables/user-settings/sudo-mode-popup.md +++ b/translations/ja-JP/data/reusables/user-settings/sudo-mode-popup.md @@ -1 +1,3 @@ -1. {% data variables.product.product_name %} パスワードの確認を促された場合は、確認します。 ![sudo モードダイアログ](/assets/images/help/settings/sudo_mode_popup.png) +{%- ifversion fpt or ghec or ghes %} +1. If prompted, confirm access to your account on {% data variables.product.product_name %}. For more information, see "[Sudo mode](/authentication/keeping-your-account-and-data-secure/sudo-mode)." +{%- endif %} diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv index 8ed3430cc9..64a2a6280e 100644 --- a/translations/log/cn-resets.csv +++ b/translations/log/cn-resets.csv @@ -109,7 +109,6 @@ translations/zh-CN/content/admin/user-management/managing-users-in-your-enterpri translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md,broken liquid tags translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,broken liquid tags -translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md,broken liquid tags translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md,broken liquid tags translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md,broken liquid tags translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,broken liquid tags @@ -386,7 +385,7 @@ translations/zh-CN/data/reusables/enterprise_installation/hardware-consideration translations/zh-CN/data/reusables/enterprise_management_console/badge_indicator.md,broken liquid tags translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,rendering error translations/zh-CN/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags -translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md,rendering error +translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md,broken liquid tags translations/zh-CN/data/reusables/gated-features/packages.md,broken liquid tags translations/zh-CN/data/reusables/gated-features/secret-scanning-partner.md,broken liquid tags translations/zh-CN/data/reusables/gated-features/secret-scanning.md,broken liquid tags @@ -404,13 +403,12 @@ translations/zh-CN/data/reusables/package_registry/authenticate_with_pat_for_con translations/zh-CN/data/reusables/package_registry/docker_registry_deprecation_status.md,Listed in localization-support#489 translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags translations/zh-CN/data/reusables/package_registry/packages-cluster-support.md,broken liquid tags -translations/zh-CN/data/reusables/pages/pages-builds-with-github-actions-public-beta.md,broken liquid tags translations/zh-CN/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md,broken liquid tags translations/zh-CN/data/reusables/repositories/enable-security-alerts.md,broken liquid tags translations/zh-CN/data/reusables/repositories/select-marketplace-apps.md,broken liquid tags -translations/zh-CN/data/reusables/saml/saml-session-oauth.md,rendering error +translations/zh-CN/data/reusables/saml/saml-session-oauth.md,broken liquid tags translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,Listed in localization-support#489 -translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,rendering error +translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags translations/zh-CN/data/reusables/scim/after-you-configure-saml.md,broken liquid tags translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags translations/zh-CN/data/reusables/secret-scanning/partner-program-link.md,broken liquid tags diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv index af5bcfc559..985c0c3891 100644 --- a/translations/log/ja-resets.csv +++ b/translations/log/ja-resets.csv @@ -175,6 +175,7 @@ translations/ja-JP/content/get-started/privacy-on-github/managing-data-use-setti translations/ja-JP/content/get-started/using-github/github-mobile.md,broken liquid tags translations/ja-JP/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,broken liquid tags translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md,broken liquid tags +translations/ja-JP/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md,broken liquid tags translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md,broken liquid tags translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md,Listed in localization-support#489 diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md index 5c660e6ecb..abe756b715 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md @@ -32,7 +32,7 @@ Building and testing your code requires a server. You can build and test updates ## About continuous integration using {% data variables.product.prodname_actions %} {% ifversion ghae %}CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on runner systems that you host. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." -{% else %} CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on {% data variables.product.prodname_dotcom %}-hosted virtual machines, or on machines that you host yourself. For more information, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)" and "[About self-hosted runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)." +{% else %} CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on {% data variables.product.prodname_dotcom %}-hosted virtual machines, or on machines that you host yourself. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)." {% endif %} You can configure your CI workflow to run when a {% data variables.product.prodname_dotcom %} event occurs (for example, when new code is pushed to your repository), on a set schedule, or when an external event occurs using the repository dispatch webhook. diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md index 96009713f3..7b7600f4fc 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md @@ -28,8 +28,8 @@ shortTitle: 构建和测试 Xamarin 应用程序 在 {% data variables.product.prodname_actions %} 托管的 macOS 运行器上有可用的 Xamarin SDK 版本的完整列表，请参阅文档： -* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles) -* [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles) +* [macOS 10.15](https://github.com/actions/runner-images/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles) +* [macOS 11](https://github.com/actions/runner-images/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles) {% data reusables.actions.macos-runner-preview %} diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md index ba2b2c2dc3..9caaa0dce2 100644 --- a/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md @@ -39,7 +39,7 @@ shortTitle: Docker 容器操作 {% ifversion ghae %} - “[Docker 容器文件系统](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)”。 {% else %} -- "[{% data variables.product.prodname_dotcom %} 的虚拟环境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners#docker-container-filesystem)" +- "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)" {% endif %} 在开始之前，您需要创建 {% data variables.product.prodname_dotcom %} 仓库。 diff --git a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 3d1ed64db0..783cdc1d3f 100644 --- a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -74,7 +74,7 @@ inputs: ### `inputs..required` -**必要** 表示操作是否需要输入参数的 `boolean`。 当参数为必要时设置为 `true`。 +**Optional** A `boolean` to indicate whether the action requires the input parameter. 当参数为必要时设置为 `true`。 ### `inputs..default` diff --git a/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md index bcc3146fbf..22323361b4 100644 --- a/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md +++ b/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md @@ -27,7 +27,7 @@ versions: **注意：** 您只能为公共存储库配置环境。 如果您将仓库从公开转换为私密，任何配置的保护规则或环境机密将被忽略， 并且您将无法配置任何环境。 如果将仓库转换回公共，您将有权访问以前配置的任何保护规则和环境机密。 -使用 {% data variables.product.prodname_ghe_cloud %} 的组织可以为私有仓库配置环境。 更多信息请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment)。 {% data reusables.enterprise.link-to-ghec-trial %} +Organizations with {% data variables.product.prodname_team %} and users with {% data variables.product.prodname_pro %} can configure environments for private repositories. 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/get-started/learning-about-github/githubs-products)”。 {% endnote %} {% endif %} @@ -72,7 +72,7 @@ versions: {% ifversion fpt or ghec %} {% note %} -**注意：**要在私有存储库中创建环境，您的组织必须使用 {% data variables.product.prodname_ghe_cloud %}。 {% data reusables.enterprise.link-to-ghec-trial %} +**Note:** Creation of an environment in a private repository is available to organizations with {% data variables.product.prodname_team %} and users with {% data variables.product.prodname_pro %}. {% endnote %} {% endif %} diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md index 5ec0aa6087..48904a1a72 100644 --- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md @@ -37,7 +37,7 @@ CircleCI 和 {% data variables.product.prodname_actions %} 都允许您创建能 - CircleCI 的自动测试并行性根据用户指定的规则或历史计时信息自动对测试进行分组。 此功能未内置于 {% data variables.product.prodname_actions %}。 - 在 Docker 容器中执行的操作对权限问题很敏感，因为容器具有不同的用户映射。 您可以通过在 *Dockerfile* 中不使用 `USER` 指令来避免这些问题。 {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} -{% else %}有关 {% data variables.product.product_name %} 托管的运行器上 Docker 文件系统的更多信息，请参阅“[ {% data variables.product.product_name %} 托管运行器的虚拟环境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)”。 +{% else %}For more information about the Docker filesystem on {% data variables.product.product_name %}-hosted runners, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)." {% endif %} ## 迁移工作流程和作业 @@ -66,10 +66,10 @@ CircleCI 提供一套具有共同依赖项的预建映像。 这些映像的 `US {% data reusables.actions.self-hosted-runners-software %} {% else %} -有关 Docker 文件系统的更多信息，请参阅“[ {% data variables.product.product_name %} 托管运行器的虚拟环境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)”。 +For more information about the Docker filesystem, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)." 有关 -{% data variables.product.prodname_dotcom %} 托管的虚拟环境中可用的工具和软件包的更多信息，请参阅“[{% data variables.product.prodname_dotcom %} 托管的运行器的规格](/actions/reference/specifications-for-github-hosted-runners/#supported-software)”。 +{% data variables.product.prodname_dotcom %}-hosted runner images, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". {% endif %} ## 使用变量和密码 @@ -287,7 +287,8 @@ jobs: steps: # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. - # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem + # See https://docs.github.com/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem + - name: Setup file system permissions run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp - uses: {% data reusables.actions.action-checkout %} diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md index 95450b215c..5ce88f9177 100644 --- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md +++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md @@ -27,7 +27,7 @@ versions: 除了工作流程文件中配置的步骤外，{% data variables.product.prodname_dotcom %} 为每个作业添加了另外两个步骤，以设置和完成作业的执行。 这些步骤以名称"设置作业"和"完成作业"记录在工作流程运行中。 -对于在 {% data variables.product.prodname_dotcom %} 托管的运行器上运行的作业，“设置作业”记录运行器虚拟环境的详细信息。 并包含一个链接，可链接到运行器机器上的预安装工具列表。 +For jobs run on {% data variables.product.prodname_dotcom %}-hosted runners, "Set up job" records details of the runner image, and includes a link to the list of preinstalled tools that were present on the runner machine. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index ece89beed5..2d10a26f12 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -105,18 +105,18 @@ MacOS 虚拟机的硬件规格： {% data variables.product.prodname_dotcom %} 托管的运行器中包含的软件工具每周更新。 更新过程需要几天时间，整个部署结束后，`主`分支上的预装软件列表将进行更新。 ### 预安装的软件 -工作流程日志包括指向准确运行器上预安装的工具的链接。 要在工作流程日志中查找此信息，请扩展 `Set up job` 部分。 在该部分下，展开 `Virtual Environment` 部分。 `Included Software` 后面的链接将说明运行器上运行该工作流程的预安装工具。 ![Installed software link](/assets/images/actions-runner-installed-software-link.png) 更多信息请参阅“[查看工作流程运行历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)”。 +工作流程日志包括指向准确运行器上预安装的工具的链接。 要在工作流程日志中查找此信息，请扩展 `Set up job` 部分。 Under that section, expand the `Runner Image` section. `Included Software` 后面的链接将说明运行器上运行该工作流程的预安装工具。 ![Installed software link](/assets/images/actions-runner-installed-software-link.png) 更多信息请参阅“[查看工作流程运行历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)”。 有关每个运行器操作系统包含的工具整个列表，请参阅以下链接： -* [Ubuntu 22.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2204-Readme.md) -* [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-Readme.md) -* [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-Readme.md) -* [Windows Server 2022](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md) -* [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md) -* [macOS 12](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-12-Readme.md) -* [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md) -* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) +* [Ubuntu 22.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2204-Readme.md) +* [Ubuntu 20.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2004-Readme.md) +* [Ubuntu 18.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu1804-Readme.md) (deprecated) +* [Windows Server 2022](https://github.com/actions/runner-images/blob/main/images/win/Windows2022-Readme.md) +* [Windows Server 2019](https://github.com/actions/runner-images/blob/main/images/win/Windows2019-Readme.md) +* [macOS 12](https://github.com/actions/runner-images/blob/main/images/macos/macos-12-Readme.md) +* [macOS 11](https://github.com/actions/runner-images/blob/main/images/macos/macos-11-Readme.md) +* [macOS 10.15](https://github.com/actions/runner-images/blob/main/images/macos/macos-10.15-Readme.md) {% data variables.product.prodname_dotcom %} 托管的运行器除了上述参考中列出的包之外，还包括操作系统的默认内置工具。 例如，Ubuntu 和 macOS 运行器除了其他默认工具之外，还包括 `grep`、`find` 和 `which`。 @@ -126,7 +126,7 @@ MacOS 虚拟机的硬件规格： - 通常，操作提供更灵活的功能，如版本选择、传递参数的能力和参数 - 它可确保工作流程中使用的工具版本无论软件更新如何，都将保持不变 -如果有您想要请求的工具，请在 [actions/virtual-environments](https://github.com/actions/virtual-environments) 打开一个议题。 此仓库还包含有关运行器上所有主要软件更新的公告。 +If there is a tool that you'd like to request, please open an issue at [actions/runner-images](https://github.com/actions/runner-images). 此仓库还包含有关运行器上所有主要软件更新的公告。 ### 安装其他软件 diff --git a/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md b/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md index 4cb3085d21..8e8b15e896 100644 --- a/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md +++ b/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md @@ -20,7 +20,7 @@ miniTocMaxHeadingLevel: 3 工作流程运行通常在不同运行之间重新使用相同的输出或下载的依赖项。 例如，Maven、Gradle、npm 和 Yarn 等软件包和依赖项管理工具都会对下载的依赖项保留本地缓存。 -{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} 托管的运行器在一个干净的虚拟环境中启动，每次都必须下载依赖项，造成网络利用率提高、运行时间延长和成本增加。 {% endif %}为帮助加快重新创建诸如依赖项的文件，{% data variables.product.prodname_dotcom %} 可以缓存您在工作流程中经常使用的文件。 +{% ifversion fpt or ghec %} Jobs on {% data variables.product.prodname_dotcom %}-hosted runners start in a clean runner image and must download dependencies each time, causing increased network utilization, longer runtime, and increased cost. {% endif %}为帮助加快重新创建诸如依赖项的文件，{% data variables.product.prodname_dotcom %} 可以缓存您在工作流程中经常使用的文件。 要缓存作业的依赖项，可以使用 {% data variables.product.prodname_dotcom %} 的 [`cache` 操作](https://github.com/actions/cache)。 该操作将创建并还原由唯一键标识的缓存。 或者，如果要缓存下面列出的包管理器，则使用其各自的 setup-* 操作时需要的配置最少，并且将为您创建和还原依赖项缓存。 diff --git a/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md index 6b2ea328fb..48c8c4b44c 100644 --- a/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md @@ -536,15 +536,16 @@ jobs: 您可以使用 `shell` 关键词覆盖运行器操作系统中默认的 shell 设置。 您可以使用内置的 `shell` 关键词，也可以自定义 shell 选项集。 内部运行的 shell 命令执行一个临时文件，其中包含 `run` 关键词中指定的命令。 -| 支持的平台 | `shell` 参数 | 描述 | 内部运行命令 | -| ------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| 所有 | `bash` | 非 Windows 平台上回退到 `sh` 的默认 shell。 指定 Windows 上的 bash shell 时，将使用 Git for Windows 随附的 bash shel。 | `bash --noprofile --norc -eo pipefail {0}` | -| 所有 | `pwsh` | PowerShell Core。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 | `pwsh -command ". '{0}'"` | -| 所有 | `python` | 执行 python 命令。 | `python {0}` | -| Linux / macOS | `sh` | 未提供 shell 且 在路径中找不到 `bash` 时的非 Windows 平台的后退行为。 | `sh -e {0}` | -| Windows | `cmd` | {% data variables.product.prodname_dotcom %} 将扩展名 `.cmd` 附加到您的脚本名称并替换 `{0}`。 | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | -| Windows | `pwsh` | 这是 Windows 上使用的默认 shell。 PowerShell Core。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 如果自托管的 Windows 运行器没有安装 _PowerShell Core_，则使用 _PowerShell Desktop_ 代替。 | `pwsh -command ". '{0}'"`. | -| Windows | `powershell` | PowerShell 桌面。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 | `powershell -command ". '{0}'"`. | +| 支持的平台 | `shell` 参数 | 描述 | 内部运行命令 | +| ------------- | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | +| Linux / macOS | unspecified | The default shell on non-Windows platforms. Note that this runs a different command to when `bash` is specified explicitly. If `bash` is not found in the path, this is treated as `sh`. | `bash -e {0}` | +| 所有 | `bash` | 非 Windows 平台上回退到 `sh` 的默认 shell。 指定 Windows 上的 bash shell 时，将使用 Git for Windows 随附的 bash shel。 | `bash --noprofile --norc -eo pipefail {0}` | +| 所有 | `pwsh` | PowerShell Core。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 | `pwsh -command ". '{0}'"` | +| 所有 | `python` | 执行 python 命令。 | `python {0}` | +| Linux / macOS | `sh` | 未提供 shell 且 在路径中找不到 `bash` 时的非 Windows 平台的后退行为。 | `sh -e {0}` | +| Windows | `cmd` | {% data variables.product.prodname_dotcom %} 将扩展名 `.cmd` 附加到您的脚本名称并替换 `{0}`。 | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | +| Windows | `pwsh` | 这是 Windows 上使用的默认 shell。 PowerShell Core。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 如果自托管的 Windows 运行器没有安装 _PowerShell Core_，则使用 _PowerShell Desktop_ 代替。 | `pwsh -command ". '{0}'"`. | +| Windows | `powershell` | PowerShell 桌面。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 | `powershell -command ". '{0}'"`. | #### 示例：使用 bash 运行脚本 @@ -793,11 +794,11 @@ strategy: fail-fast: false matrix: node: [13, 14] - os: [macos-latest, ubuntu-18.04] + os: [macos-latest, ubuntu-latest] experimental: [false] include: - node: 15 - os: ubuntu-18.04 + os: ubuntu-latest experimental: true ``` {% endraw %} diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md index d4b38b9b94..dbc7885a81 100644 --- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md @@ -146,7 +146,7 @@ Optionally, you can build custom tooling to automatically scale the self-hosted - "Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}" in the [{% data variables.product.prodname_ghe_server %}](/enterprise-server@latest/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect) or [{% data variables.product.prodname_ghe_managed %}](/github-ae@latest//admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect) documentation {%- endif %} -- You can customize the software available on your self-hosted runner machines, or configure your runners to run software similar to {% data variables.product.company_short %}-hosted runners{% ifversion ghes or ghae %} available for customers using {% data variables.product.prodname_dotcom_the_website %}{% endif %}. The software that powers runner machines for {% data variables.product.prodname_actions %} is open source. For more information, see the [`actions/runner`](https://github.com/actions/runner) and [`actions/virtual-environments`](https://github.com/actions/virtual-environments) repositories. +- You can customize the software available on your self-hosted runner machines, or configure your runners to run software similar to {% data variables.product.company_short %}-hosted runners{% ifversion ghes or ghae %} available for customers using {% data variables.product.prodname_dotcom_the_website %}{% endif %}. The software that powers runner machines for {% data variables.product.prodname_actions %} is open source. For more information, see the [`actions/runner`](https://github.com/actions/runner) and [`actions/runner-images`](https://github.com/actions/runner-images) repositories. ## Further reading diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index f19b8e5278..0dfc96abe2 100644 --- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -30,7 +30,7 @@ You can populate the runner tool cache by running a {% data variables.product.pr {% note %} -**Note:** You can only use a {% data variables.product.prodname_dotcom %}-hosted runner's tool cache for a self-hosted runner that has an identical operating system and architecture. For example, if you are using a `ubuntu-18.04` {% data variables.product.prodname_dotcom %}-hosted runner to generate a tool cache, your self-hosted runner must be a 64-bit Ubuntu 18.04 machine. For more information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[Virtual environments for GitHub-hosted runners](/free-pro-team@latest/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)." +**Note:** You can only use a {% data variables.product.prodname_dotcom %}-hosted runner's tool cache for a self-hosted runner that has an identical operating system and architecture. For example, if you are using a `ubuntu-22.04` {% data variables.product.prodname_dotcom %}-hosted runner to generate a tool cache, your self-hosted runner must be a 64-bit Ubuntu 22.04 machine. For more information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/free-pro-team@latest/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)." {% endnote %} @@ -45,14 +45,14 @@ You can populate the runner tool cache by running a {% data variables.product.pr 1. On {% data variables.product.prodname_dotcom_the_website %}, navigate to a repository that you can use to run a {% data variables.product.prodname_actions %} workflow. 1. Create a new workflow file in the repository's `.github/workflows` folder that uploads an artifact containing the {% data variables.product.prodname_dotcom %}-hosted runner's tool cache. - The following example demonstrates a workflow that uploads the tool cache for an Ubuntu 18.04 environment, using the `setup-node` action with Node.js versions 10 and 12. + The following example demonstrates a workflow that uploads the tool cache for an Ubuntu 22.04 environment, using the `setup-node` action with Node.js versions 10 and 12. ```yaml name: Upload Node.js 10 and 12 tool cache on: push jobs: upload_tool_cache: - runs-on: ubuntu-18.04 + runs-on: ubuntu-22.04 steps: - name: Clear any existing tool cache run: | diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md index c2fd95799e..d54735f4e8 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md @@ -30,6 +30,8 @@ redirect_from: 如果您的企业成员在 {% data variables.product.product_location %} 上管理自己的用户帐户，则可以将 SAML 身份验证配置为企业或组织的额外访问限制。 {% data reusables.saml.dotcom-saml-explanation %} +{% data reusables.saml.saml-accounts %} + {% data reusables.saml.about-saml-enterprise-accounts %} 更多信息请参阅“[配置企业的 SAML 单点登录](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)”。 或者，您可以使用 {% data variables.product.prodname_emus %} 来配置和管理企业成员的帐户。 为了帮助您确定 SAML SSO 或 {% data variables.product.prodname_emus %} 是否更适合您的企业，请参阅“[关于企业的身份验证](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)”。 diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md index be095b071c..f62297bd90 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md @@ -29,7 +29,11 @@ redirect_from: {% ifversion ghec %} -{% data reusables.saml.dotcom-saml-explanation %} For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." +{% data reusables.saml.dotcom-saml-explanation %} + +{% data reusables.saml.saml-accounts %} + +For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." {% data reusables.saml.about-saml-enterprise-accounts %} diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md index c16c35ee8d..a2f33afea2 100644 --- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md @@ -14,12 +14,6 @@ topics: - Security --- -{% note %} - -**注意：** 企业审核日志中 IP 地址的显示目前处于公开测试阶段，可能会发生更改。 - -{% endnote %} - ## 关于在审核日志中显示 IP 地址 默认情况下，{% data variables.product.product_name %} 不会在企业的审核日志中显示事件的源 IP 地址。 （可选）为了确保合规性并响应威胁，您可以显示与负责每个事件的参与者关联的完整 IP 地址。 参与者通常是用户，但也可以是应用程序或集成。 diff --git a/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md b/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md index 684e032555..60793424f8 100644 --- a/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md +++ b/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md @@ -35,7 +35,7 @@ The enterprise account on {% ifversion ghes %}{% data variables.product.product_ Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." {% ifversion ghec %} -Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings. +Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings. For more information, see "[Adding organizations to your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)." {% endif %} Your enterprise account allows you to manage and enforce policies for all the organizations owned by the enterprise. {% data reusables.enterprise.about-policies %} For more information, see "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)." diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md index 4f58cf00cc..033501e26f 100644 --- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md @@ -14,13 +14,14 @@ topics: - Enterprise - Organizations shortTitle: 添加组织 +permissions: Enterprise owners can add organizations to an enterprise. --- ## 关于组织 您的企业帐户可以拥有组织。 企业成员可以跨组织内的相关项目进行协作。 更多信息请参阅“[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)”。 -企业所有者可以在企业帐户设置内创建新组织，或邀请现有组织加入企业。 要将组织添加到企业，必须在企业帐户设置中创建组织。 +You can add a new or existing organization to your enterprise in your enterprise account's settings. 您只能以这种方式将组织添加到现有企业帐户。 {% data reusables.enterprise.create-an-enterprise-account %} 更多信息请参阅“[创建企业帐户](/admin/overview/creating-an-enterprise-account)”。 diff --git a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md index be38f7a365..3e825ac075 100644 --- a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md +++ b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md @@ -29,24 +29,24 @@ topics: {% data reusables.enterprise_migrations.fork-persistence %} -| 与迁移的仓库关联的数据 | 注： | -| -------------- | --------------------------------------------------------------------------------------------- | -| 用户 | 用户的 **@提及**将重写以匹配目标。 | -| 组织 | 将迁移组织的名称和详细信息。 | -| 仓库 | Git 树、blob、提交和行的链接将重写以匹配目标。 迁移程序将遵循三个仓库重定向的最大值。 | -| Wikis | 将迁移所有 wiki 数据。 | -| 团队 | 团队的 **@提及**将重写以匹配目标。 | -| 里程碑 | 将保留时间戳。 | -| 项目板 | 将迁移与仓库和拥有仓库的组织关联的项目板。 | -| 议题 | 将保留问题引用和时间戳。 | -| 问题评论 | 将针对目标实例重写评论的交叉引用。 | -| 拉取请求 | 将重写拉取请求的交叉引用以匹配目标。 将保留时间戳。 | -| 拉取请求审查 | 将迁移拉取请求审查和关联的数据。 | -| 拉取请求审查评论 | 将针对目标实例重写评论的交叉引用。 将保留时间戳。 | -| 提交注释 | 将针对目标实例重写评论的交叉引用。 将保留时间戳。 | -| 版本发布 | 将迁移所有版本数据。 | -| 在拉取请求或问题上进行的操作 | 将保留对拉取请求或问题的所有修改（例如，分配用户、重命名标题和修改标签）以及每个操作的时间戳。 | -| 文件附件 | 将迁移[问题和拉取请求上的文件附件](/articles/file-attachments-on-issues-and-pull-requests)。 在迁移过程中，您可以选择将此禁用。 | -| Web 挂钩 | 仅迁移有效的 web 挂钩。 | -| 仓库部署密钥 | 将迁移仓库部署密钥。 | -| 受保护分支 | 将迁移受保护分支设置和关联的数据。 | +| 与迁移的仓库关联的数据 | 注： | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------ | +| 用户 | 用户的 **@提及**将重写以匹配目标。 | +| 组织 | 将迁移组织的名称和详细信息。 | +| 仓库 | Git 树、blob、提交和行的链接将重写以匹配目标。 迁移程序将遵循三个仓库重定向的最大值。 Internal repositories are migrated as private repositories. Archive status is unset. | +| Wikis | 将迁移所有 wiki 数据。 | +| 团队 | 团队的 **@提及**将重写以匹配目标。 | +| 里程碑 | 将保留时间戳。 | +| 项目板 | 将迁移与仓库和拥有仓库的组织关联的项目板。 | +| 议题 | 将保留问题引用和时间戳。 | +| 问题评论 | 将针对目标实例重写评论的交叉引用。 | +| 拉取请求 | 将重写拉取请求的交叉引用以匹配目标。 将保留时间戳。 | +| 拉取请求审查 | 将迁移拉取请求审查和关联的数据。 | +| 拉取请求审查评论 | 将针对目标实例重写评论的交叉引用。 将保留时间戳。 | +| 提交注释 | 将针对目标实例重写评论的交叉引用。 将保留时间戳。 | +| 版本发布 | 将迁移所有版本数据。 | +| 在拉取请求或问题上进行的操作 | 将保留对拉取请求或问题的所有修改（例如，分配用户、重命名标题和修改标签）以及每个操作的时间戳。 | +| 文件附件 | 将迁移[问题和拉取请求上的文件附件](/articles/file-attachments-on-issues-and-pull-requests)。 在迁移过程中，您可以选择将此禁用。 | +| Web 挂钩 | 仅迁移有效的 web 挂钩。 | +| 仓库部署密钥 | 将迁移仓库部署密钥。 | +| 受保护分支 | 将迁移受保护分支设置和关联的数据。 | diff --git a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index f5756b9059..9c2487c1fc 100644 --- a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- -title: About authentication with SAML single sign-on -intro: 'You can access {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% ifversion ghec %} After you authenticate with the IdP successfully from {% data variables.product.product_name %}, you must authorize any personal access token, SSH key, or {% data variables.product.prodname_oauth_app %} you would like to access the organization''s resources.{% endif %}' +title: 关于使用 SAML 单点登录进行身份验证 +intro: 'You can access {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).' redirect_from: - /articles/about-authentication-with-saml-single-sign-on - /github/authenticating-to-github/about-authentication-with-saml-single-sign-on @@ -10,52 +10,62 @@ versions: ghec: '*' topics: - SSO -shortTitle: SAML single sign-on +shortTitle: SAML 单点登录 --- -## About authentication with SAML SSO + +## 关于使用 SAML SSO 进行身份验证 {% ifversion ghae %} -SAML SSO allows an enterprise owner to centrally control and secure access to {% data variables.product.product_name %} from a SAML IdP. When you visit {% data variables.product.product_location %} in a browser, {% data variables.product.product_name %} will redirect you to your IdP to authenticate. After you successfully authenticate with an account on the IdP, the IdP redirects you back to {% data variables.product.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access. +SAML SSO 允许企业所有者从 SAML IdP 集中控制和安全访问 {% data variables.product.product_name %}。 在浏览器中访问 {% data variables.product.product_location %} 时，{% data variables.product.product_name %} 会将用户重定向到您的 IdP 进行身份验证。 在使用 IdP 上的帐户成功进行身份验证后，IdP 会将您重定向回 {% data variables.product.product_location %}。 {% data variables.product.product_name %} 将验证 IdP 的响应，然后授予访问权限。 {% data reusables.saml.you-must-periodically-authenticate %} -If you can't access {% data variables.product.product_name %}, contact your local enterprise owner or administrator for {% data variables.product.product_name %}. You may be able to locate contact information for your enterprise by clicking **Support** at the bottom of any page on {% data variables.product.product_name %}. {% data variables.product.company_short %} and {% data variables.contact.github_support %} do not have access to your IdP, and cannot troubleshoot authentication problems. +如果您无法访问 {% data variables.product.product_name %}，请与本地企业所有者或 {% data variables.product.product_name %} 的管理员联系。 您可以在 {% data variables.product.product_name %} 上的任何页面底部单击 **Support（支持）**找到企业的联系信息。 {% data variables.product.company_short %} 和 {% data variables.contact.github_support %} 无法访问您的 IdP，并且无法解决身份验证问题。 {% endif %} {% ifversion fpt or ghec %} -{% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your personal account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}. +{% data reusables.saml.dotcom-saml-explanation %} 组织所有者可以邀请您在 {% data variables.product.prodname_dotcom %} 上的个人帐户加入其使用 SAML SSO 的组织，这样您可以对该组织做出贡献，并且保留您在 {% data variables.product.prodname_dotcom %} 上的现有身份和贡献。 -If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will use a new account that is provisioned for you. {% data reusables.enterprise-accounts.emu-more-info-account %} +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will instead use a new account that is provisioned for you and controlled by your enterprise. {% data reusables.enterprise-accounts.emu-more-info-account %} - -When you access resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources. +When you access private resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. 在 IdP 上成功验证您的帐户后，IdP 会将您重定向回到 {% data variables.product.prodname_dotcom %}，您可以在那里访问组织的资源。 {% data reusables.saml.outside-collaborators-exemption %} -If you have recently authenticated with your organization's SAML IdP in your browser, you are automatically authorized when you access a {% data variables.product.prodname_dotcom %} organization that uses SAML SSO. If you haven't recently authenticated with your organization's SAML IdP in your browser, you must authenticate at the SAML IdP before you can access the organization. +如果您最近在浏览器中使用组织的 SAML IdP 进行过身份验证，则在访问使用 SAML SSO 的 {% data variables.product.prodname_dotcom %} 组织时会自动获得授权。 如果您最近没有在浏览器中使用组织的 SAML IdP 进行身份验证，则必须在 SAML IdP 进行身份验证后才可访问组织。 {% data reusables.saml.you-must-periodically-authenticate %} -To use the API or Git on the command line to access protected content in an organization that uses SAML SSO, you will need to use an authorized personal access token over HTTPS or an authorized SSH key. +## Linked SAML identities -If you don't have a personal access token or an SSH key, you can create a personal access token for the command line or generate a new SSH key. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" or "[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)." +When you authenticate with your IdP account and return to {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_dotcom %} will record a link in the organization or enterprise between your {% data variables.product.prodname_dotcom %} personal account and the SAML identity you signed into. This linked identity is used to validate your membership in that organization, and depending on your organization or enterprise setup, is also used to determine which organizations and teams you're a member of as well. Each {% data variables.product.prodname_dotcom %} account can be linked to exactly one SAML identity per organization. Likewise, each SAML identity can be linked to exactly one {% data variables.product.prodname_dotcom %} account in an organization. -To use a new or existing personal access token or SSH key with an organization that uses or enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." +If you sign in with a SAML identity that is already linked to another {% data variables.product.prodname_dotcom %} account, you will receive an error message indicating that you cannot sign in with that SAML identity. This situation can occur if you are attempting to use a new {% data variables.product.prodname_dotcom %} account to work inside of your organization. If you didn't intend to use that SAML identity with that {% data variables.product.prodname_dotcom %} account, then you'll need to sign out of that SAML identity and then repeat the SAML login. If you do want to use that SAML identity with your {% data variables.product.prodname_dotcom %} account, you'll need to ask your admin to unlink your SAML identity from your old account, so that you can link it to your new account. Depending on the setup of your organization or enterprise, your admin may also need to reassign your identity within your SAML provider. 更多信息请参阅“[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)”。 -## About {% data variables.product.prodname_oauth_apps %}, {% data variables.product.prodname_github_apps %}, and SAML SSO +If the SAML identity you sign in with does not match the SAML identity that is currently linked to your {% data variables.product.prodname_dotcom %} account, you'll receive a warning that you are about to relink your account. Because your SAML identity is used to govern access and team membership, continuing with the new SAML identity can cause you to lose access to teams and organizations inside of {% data variables.product.prodname_dotcom %}. Only continue if you know that you're supposed to use that new SAML identity for authentication in the future. -You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %} or {% data variables.product.prodname_github_app %} to access an organization that uses or enforces SAML SSO. You can create an active SAML session by navigating to `https://github.com/orgs/ORGANIZATION-NAME/sso` in your browser. +## Authorizing PATs and SSH keys with SAML SSO -After an enterprise or organization owner enables or enforces SAML SSO for an organization, and after you authenticate via SAML for the first time, you must reauthorize any {% data variables.product.prodname_oauth_apps %} or {% data variables.product.prodname_github_apps %} that you previously authorized to access the organization. +要在命令行上使用 API 或 Git 访问使用 SAML SSO 的组织中受保护的内容，需要使用授权的 HTTPS 个人访问令牌或授权的 SSH 密钥。 -To see the {% data variables.product.prodname_oauth_apps %} you've authorized, visit your [{% data variables.product.prodname_oauth_apps %} page](https://github.com/settings/applications). To see the {% data variables.product.prodname_github_apps %} you've authorized, visit your [{% data variables.product.prodname_github_apps %} page](https://github.com/settings/apps/authorizations). +如果没有个人访问令牌或 SSH 密钥，可以创建用于命令行的个人访问令牌或生成新的 SSH 密钥。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”或“[生成新的 SSH 密钥并添加到 ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”。 + +要对使用或实施 SAML SSO 的组织使用新的或现有的个人访问令牌或 SSH 密钥，需要授权该令牌或授权 SSH 密钥用于 SAML SSO 组织。 更多信息请参阅“[授权个人访问令牌用于 SAML 单点登录](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)”或“[授权 SSH 密钥用于 SAML 单点登录](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)”。 + +## 关于 {% data variables.product.prodname_oauth_apps %}、{% data variables.product.prodname_github_apps %} 和 SAML SSO + +每次授权 {% data variables.product.prodname_oauth_app %} 或 {% data variables.product.prodname_github_app %} 访问使用或实施 SAML SSO 的组织时，您必须有一个活动的 SAML 会话。 您可以通过导航到浏览器中的 `https://github.com/orgs/ORGANIZATION-NAME/sso` 来创建活动的 SAML 会话。 + +在企业或组织所有者为组织启用或强制实施 SAML SSO 后，以及在首次通过 SAML 进行身份验证后，您必须重新授权以前有权访问该组织的任何 {% data variables.product.prodname_oauth_apps %} 或 {% data variables.product.prodname_github_apps %}。 + +要查看您授权的 {% data variables.product.prodname_oauth_apps %} ，请访问您的 [{% data variables.product.prodname_oauth_apps %} 页面](https://github.com/settings/applications)。 要查看您授权的 {% data variables.product.prodname_github_apps %} ，请访问您的 [{% data variables.product.prodname_github_apps %} 页面](https://github.com/settings/apps/authorizations)。 {% endif %} -## Further reading +## 延伸阅读 -{% ifversion ghec %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} -{% ifversion ghae %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} +{% ifversion ghec %}- "[关于使用 SAML 单点登录管理身份和访问](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} +{% ifversion ghae %}- "[关于企业的身份和访问权限管理](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md index 6a231f83f3..a411922d2f 100644 --- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md +++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md @@ -14,8 +14,6 @@ topics: - SSH --- -## About SSH - {% data reusables.ssh.about-ssh %} For more information about SSH, see [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) on Wikipedia. When you set up SSH, you will need to generate a new private SSH key and add it to the SSH agent. You must also add the public SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)." diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md index d7656c3cd8..9b8b0891ee 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md @@ -23,7 +23,7 @@ To maintain the security of your account when you perform a potentially sensitiv - Authorization of a third-party application - Addition of a new SSH key -After you authenticate to perform a sensitive action, your session is temporarily in "sudo mode." In sudo mode, you can perform sensitive actions without authentication. {% data variables.product.product_location %} will wait a few hours before prompting you for authentication again. During this time, any sensitive action that you perform will reset the timer. +After you authenticate to perform a sensitive action, your session is temporarily in "sudo mode." In sudo mode, you can perform sensitive actions without authentication. {% data variables.product.product_name %} will wait a few hours before prompting you for authentication again. During this time, any sensitive action that you perform will reset the timer. {% ifversion ghes %} @@ -41,13 +41,16 @@ After you authenticate to perform a sensitive action, your session is temporaril To confirm access for sudo mode, you {% ifversion totp-and-mobile-sudo-challenge %}can{% else %}must{% endif %} authenticate with your password.{% ifversion totp-and-mobile-sudo-challenge %} Optionally, you can use a different authentication method, like {% ifversion fpt or ghec %}a security key, {% data variables.product.prodname_mobile %}, or a 2FA code{% elsif ghes %}a security key or a 2FA code{% endif %}.{% endif %} -{% ifversion totp-and-mobile-sudo-challenge %} +{%- ifversion totp-and-mobile-sudo-challenge %} - [Confirming access using a security key](#confirming-access-using-a-security-key) {%- ifversion fpt or ghec %} - [Confirming access using GitHub Mobile](#confirming-access-using-github-mobile) {%- endif %} - [Confirming access using a 2FA code](#confirming-access-using-a-2fa-code) - [Confirming access using your password](#confirming-access-using-your-password) +{%- endif %} + +{% ifversion totp-and-mobile-sudo-challenge %} ### Confirming access using a security key @@ -57,8 +60,6 @@ When prompted to authenticate for sudo mode, click **Use security key**, then fo ![Screenshot of security key option for sudo mode](/assets/images/help/settings/sudo_mode_prompt_security_key.png) -{% endif %} - {% ifversion fpt or ghec %} ### Confirming access using {% data variables.product.prodname_mobile %} @@ -75,11 +76,9 @@ You must install and sign into {% data variables.product.prodname_mobile %} to c {% endif %} -{% ifversion totp-and-mobile-sudo-challenge %} - ### Confirming access using a 2FA code -You must configure 2FA using a TOTP mobile app{% ifversion fpt or ghec %} or text messages{% endif %} to confirm access to your account for sudo mode using a 2FA code. 更多信息请参阅“[配置双重身份验证](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-totp-mobile-app)”。 +You must configure 2FA using a TOTP mobile app{% ifversion fpt or ghec %} or text messages{% endif %} to confirm access to your account for sudo mode using a 2FA code. 更多信息请参阅“[配置双重身份验证](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)”。 When prompted to authenticate for sudo mode, type the authentication code from your TOTP mobile app{% ifversion fpt or ghec %} or the text message{% endif %}, then click **Verify**. diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md index 3f5d7106bf..3df17ec3a9 100644 --- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md +++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md @@ -34,11 +34,11 @@ topics: ## 依赖项 -如果您使用的容器缺少某些依赖项（例如，Git 必须安装并添加到 PATH 变量），您可能难以运行 {% data variables.product.prodname_code_scanning %}。 如果遇到依赖项问题，请查看通常包含在 {% data variables.product.prodname_dotcom %} 虚拟环境中的软件列表。 有关更多信息，请在以下位置查看特定于版本的 `readme` 文件： +如果您使用的容器缺少某些依赖项（例如，Git 必须安装并添加到 PATH 变量），您可能难以运行 {% data variables.product.prodname_code_scanning %}。 If you encounter dependency issues, review the list of software typically included on {% data variables.product.prodname_dotcom %}'s runner images. 有关更多信息，请在以下位置查看特定于版本的 `readme` 文件： -* Linux: https://github.com/actions/virtual-environments/tree/main/images/linux -* macOS: https://github.com/actions/virtual-environments/tree/main/images/macos -* Windows: https://github.com/actions/virtual-environments/tree/main/images/win +* Linux: https://github.com/actions/runner-images/tree/main/images/linux +* macOS: https://github.com/actions/runner-images/tree/main/images/macos +* Windows: https://github.com/actions/runner-images/tree/main/images/win ## 示例工作流程 diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index c900d9dfe1..5bbb673719 100644 --- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -88,7 +88,7 @@ For repositories where {% data variables.product.prodname_dependabot_security_up ## Access to {% data variables.product.prodname_dependabot_alerts %} -You can see all of the alerts that affect a particular project{% ifversion fpt or ghec %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)." +You can see all of the alerts that affect a particular project{% ifversion fpt or ghec %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)." By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} never publicly discloses insecure dependencies for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working with repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." {% endif %} @@ -102,5 +102,5 @@ You can also see all the {% data variables.product.prodname_dependabot_alerts %} ## Further reading - "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" -- "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} {% ifversion fpt or ghec %}- "[Privacy on {% data variables.product.prodname_dotcom %}](/get-started/privacy-on-github)"{% endif %} diff --git a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md index b94ae151ca..0344ac5067 100644 --- a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -93,7 +93,7 @@ You can configure {% data variables.product.prodname_dependabot %} to ignore spe ## Further reading - "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" -- "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" - "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes > 3.2 %} - "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/translations/zh-CN/content/code-security/getting-started/github-security-features.md b/translations/zh-CN/content/code-security/getting-started/github-security-features.md index 19978f53ae..bc033f52bd 100644 --- a/translations/zh-CN/content/code-security/getting-started/github-security-features.md +++ b/translations/zh-CN/content/code-security/getting-started/github-security-features.md @@ -58,8 +58,15 @@ The dependency graph allows you to explore the ecosystems and packages that your You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +{% ifversion security-overview-displayed-alerts %} +### Security overview + +The security overview allows you to review security configurations and alerts, making it easy to identify the repositories and organizations at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + +{% else %} ### Security overview for repositories -For all public repositories, the security overview shows which security features are enabled for the repository, and offers the option to configure any available security features that are not currently enabled. +The security overview shows which security features are enabled for the repository, and offers you the option of configuring any available security features that are not already enabled. +{% endif %} ## Available with {% data variables.product.prodname_GH_advanced_security %} @@ -67,7 +74,7 @@ For all public repositories, the security overview shows which security features The following {% data variables.product.prodname_GH_advanced_security %} features are available and free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can use the full set of features in any of their repositories. For a list of the features available with {% data variables.product.prodname_ghe_cloud %}, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/github-security-features#available-with-github-advanced-security). {% elsif ghec %} -Many {% data variables.product.prodname_GH_advanced_security %} features are available and free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations within an enterprise that has a {% data variables.product.prodname_GH_advanced_security %} license can use all the following features on their repositories. {% data reusables.advanced-security.more-info-ghas %} +Many {% data variables.product.prodname_GH_advanced_security %} features are available and free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations within an enterprise that have a {% data variables.product.prodname_GH_advanced_security %} license can use the following features on all their repositories. {% data reusables.advanced-security.more-info-ghas %} {% elsif ghes %} {% data variables.product.prodname_GH_advanced_security %} features are available for enterprises with a license for {% data variables.product.prodname_GH_advanced_security %}. The features are restricted to repositories owned by an organization. {% data reusables.advanced-security.more-info-ghas %} @@ -86,7 +93,7 @@ Automatically detect security vulnerabilities and coding errors in new or modifi Automatically detect leaked secrets across all public repositories. {% data variables.product.company_short %} informs the relevant service provider that the secret may be compromised. For details of the supported secrets and service providers, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)." {% endif %} -{% ifversion not fpt %} +{% ifversion ghec or ghes or ghae %} ### {% data variables.product.prodname_secret_scanning_GHAS_caps %} {% ifversion ghec %} @@ -100,12 +107,12 @@ Automatically detect tokens or credentials that have been checked into a reposit Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." -{% ifversion ghec or ghes or ghae %} -### Security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %}, enterprises,{% endif %} and teams +{% ifversion security-overview-displayed-alerts %} -{% ifversion ghec %} -Available only with a license for {% data variables.product.prodname_GH_advanced_security %}. -{% endif %} +{% elsif fpt %} + +{% else %} +### Security overview for organizations{% ifversion ghes > 3.4 or ghae-issue-6199 %}, enterprises,{% endif %} and teams Review the security configuration and alerts for your organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." {% endif %} diff --git a/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md b/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md index 155ef044ab..e560122037 100644 --- a/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md +++ b/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md @@ -123,7 +123,7 @@ For more information, see "[Managing security and analysis settings for your org {% data variables.product.prodname_code_scanning_capc %} is configured at the repository level. 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)." ## Next steps -You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." {% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} diff --git a/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md b/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md index 9d2fbc8235..ec95d618b2 100644 --- a/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md +++ b/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md @@ -132,7 +132,7 @@ You can set up {% data variables.product.prodname_code_scanning %} to automatica {% endif %} ## Next steps -You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." {% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} diff --git a/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md b/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md index d6d8def31e..481ec138e4 100644 --- a/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md +++ b/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md @@ -91,7 +91,7 @@ For more information about viewing and resolving {% data variables.product.prodn Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." -{% ifversion ghec or ghes %} +{% ifversion ghec or ghes or ghae-issue-5503 %} You can use the security overview to see an organization-level view of which repositories have enabled {% data variables.product.prodname_secret_scanning %} and the alerts found. For more information, see "[Viewing the security overview](/code-security/security-overview/viewing-the-security-overview)." {% endif %} diff --git a/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md b/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md index 158d08df6b..75d1ea845f 100644 --- a/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md @@ -43,7 +43,7 @@ shortTitle: 关于安全概述 {% ifversion security-overview-views %} -在安全概述中，在组织和存储库级别，都有特定安全功能（如机密扫描警报和代码扫描警报）的专用视图。 您可以使用这些视图将分析限制为一组特定的警报，并使用特定于每个视图的一系列筛选器进一步缩小结果范围。 例如，在机密扫描警报视图中，可以使用`机密类型`筛选器仅查看特定机密（如 GitHub 个人访问令牌）的机密扫描警报。 在存储库级别，您可以使用安全概述来评估特定存储库的当前安全状态，并配置存储库中尚未使用的任何其他安全功能。 +In the security overview, there are dedicated views for each type of security alert, such as Dependabot, code scanning, and secret scanning alerts. 您可以使用这些视图将分析限制为一组特定的警报，并使用特定于每个视图的一系列筛选器进一步缩小结果范围。 例如，在机密扫描警报视图中，可以使用`机密类型`筛选器仅查看特定机密（如 GitHub 个人访问令牌）的机密扫描警报。 在存储库级别，您可以使用安全概述来评估特定存储库的当前安全状态，并配置存储库中尚未使用的任何其他安全功能。 {% endif %} diff --git a/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md index e20d8f2f8d..4a98ff5db5 100644 --- a/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md +++ b/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md @@ -25,6 +25,10 @@ shortTitle: 筛选警报 可以使用安全概述中的筛选器，根据一系列因素（如警报风险级别、警报类型和功能启用）缩小关注范围。 根据特定视图以及是在组织、团队还是存储库级别进行分析，可以使用不同的筛选器。 +{% note %} +{% data reusables.security-overview.information-varies-GHAS %} +{% endnote %} + ## 按仓库过滤 在所有组织级别和团队级别视图中可用。 diff --git a/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md b/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md index e095481513..714bb97866 100644 --- a/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md +++ b/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md @@ -21,6 +21,8 @@ shortTitle: 查看安全性概述 {% data reusables.security-overview.beta %} {% endif %} +{% data reusables.security-overview.information-varies-GHAS %} + ## 查看组织的安全概述 {% data reusables.organizations.navigate-to-org %} diff --git a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md index 673b819f7d..8ad804ed69 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md @@ -34,7 +34,7 @@ topics: 3. 每个构建都应在新的环境中启动，这样受损的构建不会持续影响将来的构建。 -{% data variables.product.prodname_actions %} 可以帮助您满足这些功能。 构建说明与代码一起存储在存储库中。 您可以选择在哪个环境中运行构建，包括 Windows、Mac、Linux 或您自己托管的运行器。 每个构建都从一个新的虚拟环境开始，这使得攻击很难在构建环境中持续存在。 +{% data variables.product.prodname_actions %} 可以帮助您满足这些功能。 构建说明与代码一起存储在存储库中。 您可以选择在哪个环境中运行构建，包括 Windows、Mac、Linux 或您自己托管的运行器。 Each build starts with a fresh runner image, making it difficult for an attack to persist in your build environment. 除了安全优势之外， {% data variables.product.prodname_actions %} 还允许您手动、定期或在存储库中的 git 事件上触发构建，以实现频繁、快速的构建。 diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index e015ee9db5..6b7f53bdc4 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -110,7 +110,7 @@ shortTitle: 探索依赖项 ## 延伸阅读 - “[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)” -- “[查看和更新 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)”{% ifversion ghec %} +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% ifversion ghec %} - "[查看用于组织的洞见](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %}{% ifversion fpt or ghec %} - "[了解 {% data variables.product.prodname_dotcom %} 如何使用和保护数据](/get-started/privacy-on-github)" {% endif %} diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md index 545f5ff05f..38467f41a7 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md @@ -138,22 +138,18 @@ shortTitle: 创建代码空间 gh codespace create ``` -系统将提示您选择仓库、分支和计算机类型（如果有多个可用）。 - -{% note %} - -**注意**：目前，{% data variables.product.prodname_cli %} 不允许在创建代码空间时选择开发容器配置。 如果要选择特定的开发容器配置，请使用 {% data variables.product.prodname_dotcom %} Web 界面创建代码空间。 有关更多信息，请单击此页面顶部的“Web browser（Web 浏览器）”选项卡。 - -{% endnote %} +You are prompted to choose a repository, a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available). 或者，您可以使用标志来指定部分或全部选项： ```shell -gh codespace create -r owner/repo -b branch -m machine-type +gh codespace create -r owner/repo -b branch --devcontainer-path path -m machine-type ``` In this example, replace `owner/repo` with the repository identifier. 将 `branch` 替换为您希望在代码空间中最初检出的分支的名称或提交的完整 SHA 哈希。 如果使用 `-r` 标志而不使用 `b` 标志，则将从默认分支创建代码空间。 +Replace `path` with the path to the dev container configuration file you want to use for the new codespace. If you omit this flag and more than one dev container file is available you will be prompted to choose one from a list. For more information about the dev container configuration file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." + 将 `machine-type` 替换为可用计算机类型的有效标识符。 标识符是字符串，例如：`basicLinux32gb` 和 `standardLinux32gb`。 可用的计算机类型取决于仓库、您的个人帐户和您的位置。 如果输入无效或不可用的计算机类型，则错误消息中将显示可用类型。 如果省略此标志，并且有多个计算机类型可用，系统将提示您从列表中选择一个计算机类型。 For full details of the options for this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_create). diff --git a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md index f2846a532e..ccddb6efac 100644 --- a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -19,6 +19,8 @@ topics: 使用 wiki，可以像在 {% data variables.product.product_name %} 的任何其他位置一样编写内容。 更多信息请参阅“[在 {% data variables.product.prodname_dotcom %} 上编写和设置格式](/articles/getting-started-with-writing-and-formatting-on-github)”。 我们使用[开源标记库](https://github.com/github/markup)将不同的格式转换为 HTML，以便选择使用 Markdown 或任何其他支持的格式编写。 +{% data reusables.getting-started.math-and-diagrams %} + {% ifversion fpt or ghes or ghec %}如果您在公共仓库中创建 wiki，则该 wiki 可供{% ifversion ghes %}具有 {% data variables.product.product_location %} 访问权限的任何人{% else %}公共{% endif %}访问。 {% endif %}如果您在私有{% ifversion ghec or ghes %} 或内部{% endif %} 存储库中创建 Wiki，则仅有权访问该仓库的{% ifversion fpt or ghes or ghec %}人员{% elsif ghae %}企业成员{% endif %} 才能访问该 Wiki。 更多信息请参阅“[设置仓库可见性](/articles/setting-repository-visibility)”。 您可以直接在 {% data variables.product.product_name %} 上编辑 wikis，也可在本地编辑 wiki 文件。 默认情况下，只有能够写入仓库的人才可更改 wikis，但您可以允许 {% data variables.product.product_location %} 上的每个人参与{% ifversion ghae %}内部{% else %}公共{% endif %}仓库中的 wiki。 更多信息请参阅“[更改 wikis 的访问权限](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)”。 diff --git a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md index 35ee65fb7c..7c18cb71d1 100644 --- a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md +++ b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md @@ -45,6 +45,11 @@ Wikis 可显示 PNG、JPEG 和 GIF 图片。 [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]] +{% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7647 %} +## Adding mathematical expressions and diagrams{% endif %} + +{% data reusables.getting-started.math-and-diagrams %} + ## 受支持的 MediaWiki 格式 无论您的 wiki 页面以哪种标记语言编写，始终可使用某些 MediaWiki 语法。 diff --git a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index d6eaa28728..d3c60ccc0e 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -1190,9 +1190,9 @@ Key | Type | Description `commits[][author][email]`|`string` | The git author's email address. `commits[][url]`|`url` | URL that points to the commit API resource. `commits[][distinct]`|`boolean` | Whether this commit is distinct from any that have been pushed before. -`commits[][added]`|`array` | An array of files added in the commit. -`commits[][modified]`|`array` | An array of files modified by the commit. -`commits[][removed]`|`array` | An array of files removed in the commit. +`commits[][added]`|`array` | An array of files added in the commit. For extremely large commits where {% data variables.product.product_name %} is unable to calculate this list in a timely manner, this may be empty even if files were added. +`commits[][modified]`|`array` | An array of files modified by the commit. For extremely large commits where {% data variables.product.product_name %} is unable to calculate this list in a timely manner, this may be empty even if files were modified. +`commits[][removed]`|`array` | An array of files removed in the commit. For extremely large commits where {% data variables.product.product_name %} is unable to calculate this list in a timely manner, this may be empty even if files were removed. `pusher` | `object` | The user who pushed the commits. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} diff --git a/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md index ec6b3b6496..f2774b816b 100644 --- a/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md @@ -32,38 +32,28 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th - **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." -{% ifversion ghec or ghes %} +{% ifversion ghes < 3.7 or ghae %} + - **Security overview** - Review the security configuration and alerts for an organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." {% endif %} {% ifversion fpt or ghec %} The table below summarizes the availability of {% data variables.product.prodname_GH_advanced_security %} features for public and private repositories. -{% ifversion fpt %} | | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} | | :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: | | Code scanning | Yes | No | Yes | | Secret scanning | Yes **(limited functionality only)** | No | Yes | | Dependency review | Yes | No | Yes | -{% endif %} -{% ifversion ghec %} -| | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} | -| :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: | -| Code scanning | Yes | No | Yes | -| Secret scanning | Yes **(limited functionality only)** | No | Yes | -| Dependency review | Yes | No | Yes | -| Security overview | No | No | Yes | -{% endif %} - {% endif %} For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." For an overview of all security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." {% ifversion fpt or ghec %} -{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% ifversion ghec %}, except for the security overview{% endif %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access to an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} +{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} {% endif %} -{% ifversion ghes > 3.1 or ghec %} +{% ifversion ghes > 3.1 or ghec or ghae %} ## Deploying GitHub Advanced Security in your enterprise To learn about what you need to know to plan your {% data variables.product.prodname_GH_advanced_security %} deployment at a high level and to review the rollout phases we recommended, see "[Adopting {% data variables.product.prodname_GH_advanced_security %} at scale](/code-security/adopting-github-advanced-security-at-scale)." diff --git a/translations/zh-CN/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md b/translations/zh-CN/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md index b8025330c8..3b257f4052 100644 --- a/translations/zh-CN/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md +++ b/translations/zh-CN/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md @@ -45,5 +45,5 @@ When you enable data use for your private repository, you'll be able to access t ## Further reading - "[About {% data variables.product.prodname_dotcom %}'s use of your data](/articles/about-github-s-use-of-your-data)" -- "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" diff --git a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md index 38d0e5a1c1..7d3c8e4123 100644 --- a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md +++ b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md @@ -8,7 +8,7 @@ shortTitle: 创建图表 ## 关于创建图表 -您可以使用三种不同的语法在 Markdown 中创建图表：geoJSON、topoJSON 和 ASCII STL。 +您可以使用三种不同的语法在 Markdown 中创建图表：geoJSON、topoJSON 和 ASCII STL。 Diagram rendering is available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, wikis, and Markdown files. ## 创建 Mermaid 图表 diff --git a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md index 02842bf19c..ea48c85260 100644 --- a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md +++ b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md @@ -6,10 +6,14 @@ versions: shortTitle: 数学表达式 --- +## About writing mathematical expressions + 为了清晰地沟通数学表达式，{% data variables.product.product_name %} 在 Markdown 中支持 LaTeX 格式的数学。 更多信息请参阅维基教科书中的 [LaTeX/Math](http://en.wikibooks.org/wiki/LaTeX/Mathematics)。 {% data variables.product.company_short %} 的数学渲染能力使用 MathJax；这是一个开源、基于JavaScript 的显示引擎。 MathJax 支持广泛的 LaTeX 宏，以及几个有用的可访问性扩展。 更多信息请参阅 [MathJax 文档](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) 和 [MathJax 辅助功能扩展文档](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide)。 +Mathematical expressions rendering is available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, {% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7647 %}wikis, {% endif %}and Markdown files. + ## 编写内联表达式 要在文本中包含内联的数学表达式，请使用美元符号 `$` 分隔表达式。 diff --git a/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md b/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md index 76d117a1a5..9a6394f8aa 100644 --- a/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md @@ -33,7 +33,6 @@ shortTitle: 使用 GraphQL 建立调用 ``` repo -repo_deployment read:packages read:org read:public_key diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index 4b67ae1211..a7104de20b 100644 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -60,123 +60,123 @@ shortTitle: 存储库角色 {% endnote %} {% endif %} -| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:-----:|:-------------------------------------------------------------------:| -| 管理[个人](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)、[团队](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)和[外部协作者](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)的存储库访问权限 | | | | | **X** | -| 从人员或团队的已分配仓库拉取 | **X** | **X** | **X** | **X** | **X** | -| 复刻人员或团队的已分配仓库 | **X** | **X** | **X** | **X** | **X** | -| 编辑和删除自己的评论 | **X** | **X** | **X** | **X** | **X** | -| 打开议题 | **X** | **X** | **X** | **X** | **X** | -| 关闭自己打开的议题 | **X** | **X** | **X** | **X** | **X** | -| 重新打开自己关闭的议题 | **X** | **X** | **X** | **X** | **X** | -| 受理议题 | **X** | **X** | **X** | **X** | **X** | -| 从团队已分配仓库的复刻发送拉取请求 | **X** | **X** | **X** | **X** | **X** | -| 提交拉取请求审查 | **X** | **X** | **X** | **X** | **X** | -| 查看已发布的版本 | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| 查看 [GitHub Actions 工作流程运行](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** +| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------:|:------:|:------:|:------:|:--------------------------------------------------------------------:| +| 管理[个人](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)、[团队](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)和[外部协作者](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)的存储库访问权限 | | | | | **✔️** | +| 从人员或团队的已分配仓库拉取 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 复刻人员或团队的已分配仓库 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 编辑和删除自己的评论 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 打开议题 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 关闭自己打开的议题 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 重新打开自己关闭的议题 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 受理议题 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 从团队已分配仓库的复刻发送拉取请求 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 提交拉取请求审查 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 查看已发布的版本 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| 查看 [GitHub Actions 工作流程运行](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** {% endif %} -| 编辑公共仓库中的 Wiki | **X** | **X** | **X** | **X** | **X** | -| 编辑私有仓库中的 Wiki | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| [举报滥用或垃圾内容](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +| 编辑公共仓库中的 Wiki | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 编辑私有仓库中的 Wiki | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| [举报滥用或垃圾内容](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** {% endif %} -| 应用/忽略标签 | | **X** | **X** | **X** | **X** | -| 创建、编辑、删除标签 | | | **X** | **X** | **X** | -| 关闭、重新打开和分配所有议题与拉取请求 | | **X** | **X** | **X** | **X** | -| [在拉取请求上启用和禁用自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** | -| 应用里程碑 | | **X** | **X** | **X** | **X** | -| 标记[重复的议题和拉取请求](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | -| 申请[拉取请求审查](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| 合并[拉取请求](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | -| 推送到（写入）人员或团队的已分配仓库 | | | **X** | **X** | **X** | -| 编辑和删除任何人对提交、拉取请求和议题的评论 | | | **X** | **X** | **X** | -| [隐藏任何人的评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [锁定对话](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | -| 转让议题（更多信息请参阅“[将议题转让给其他仓库](/articles/transferring-an-issue-to-another-repository)”） | | | **X** | **X** | **X** | -| [作为仓库的指定代码所有者](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [将拉取请求草稿标记为可供审查](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| [将拉取请求转换为草稿](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| 提交影响拉取请求可合并性的审查 | | | **X** | **X** | **X** | -| 对拉取请求[应用建议的更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) | | | **X** | **X** | **X** | -| 创建[状态检查](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| 创建、编辑、运行、重新运行和取消 [GitHub Actions 工作流程](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** +| 应用/忽略标签 | | **✔️** | **✔️** | **✔️** | **✔️** | +| 创建、编辑、删除标签 | | | **✔️** | **✔️** | **✔️** | +| 关闭、重新打开和分配所有议题与拉取请求 | | **✔️** | **✔️** | **✔️** | **✔️** | +| [在拉取请求上启用和禁用自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **✔️** | **✔️** | **✔️** | +| 应用里程碑 | | **✔️** | **✔️** | **✔️** | **✔️** | +| 标记[重复的议题和拉取请求](/articles/about-duplicate-issues-and-pull-requests) | | **✔️** | **✔️** | **✔️** | **✔️** | +| 申请[拉取请求审查](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **✔️** | **✔️** | **✔️** | **✔️** | +| 合并[拉取请求](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **✔️** | **✔️** | **✔️** | +| 推送到（写入）人员或团队的已分配仓库 | | | **✔️** | **✔️** | **✔️** | +| 编辑和删除任何人对提交、拉取请求和议题的评论 | | | **✔️** | **✔️** | **✔️** | +| [隐藏任何人的评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **✔️** | **✔️** | **✔️** | +| [锁定对话](/communities/moderating-comments-and-conversations/locking-conversations) | | | **✔️** | **✔️** | **✔️** | +| 转让议题（更多信息请参阅“[将议题转让给其他仓库](/articles/transferring-an-issue-to-another-repository)”） | | | **✔️** | **✔️** | **✔️** | +| [作为仓库的指定代码所有者](/articles/about-code-owners) | | | **✔️** | **✔️** | **✔️** | +| [将拉取请求草稿标记为可供审查](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | +| [将拉取请求转换为草稿](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | +| 提交影响拉取请求可合并性的审查 | | | **✔️** | **✔️** | **✔️** | +| 对拉取请求[应用建议的更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) | | | **✔️** | **✔️** | **✔️** | +| 创建[状态检查](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| 创建、编辑、运行、重新运行和取消 [GitHub Actions 工作流程](/actions/automating-your-workflow-with-github-actions/) | | | **✔️** | **✔️** | **✔️** {% endif %} -| 创建和编辑发行版 | | | **X** | **X** | **X** | -| 查看发行版草稿 | | | **X** | **X** | **X** | -| 编辑仓库的说明 | | | | **X** | **X** |{% ifversion fpt or ghae or ghec %} -| [查看和安装包](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [发布包](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package) | | | | | **X** |{% endif %} -| 管理[主题](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| 启用 wiki 和限制 wiki 编辑器 | | | | **X** | **X** | -| 启用项目板 | | | | **X** | **X** | -| 配置[拉取请求合并](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| 配置[ {% data variables.product.prodname_pages %} 的发布源](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [管理分支保护规则](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **X** | -| [推送到受保护分支](/articles/about-protected-branches) | | | | **X** | **X** | -| 合并受保护分支上的拉取请求（即使没有批准审查） | | | | | **X** |{% ifversion fpt or ghes > 3.4 or ghae-issue-6337 or ghec %} -| 创建与[标记保护规则](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)匹配的标记 | | | | **X** | **X** | -| 删除与[标记保护规则](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)匹配的标记 | | | | | **X** +| 创建和编辑发行版 | | | **✔️** | **✔️** | **✔️** | +| 查看发行版草稿 | | | **✔️** | **✔️** | **✔️** | +| 编辑仓库的说明 | | | | **✔️** | **✔️** |{% ifversion fpt or ghae or ghec %} +| [查看和安装包](/packages/publishing-and-managing-packages) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [发布包](/packages/publishing-and-managing-packages/publishing-a-package) | | | **✔️** | **✔️** | **✔️** | +| [删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package) | | | | | **✔️** |{% endif %} +| 管理[主题](/articles/classifying-your-repository-with-topics) | | | | **✔️** | **✔️** | +| 启用 wiki 和限制 wiki 编辑器 | | | | **✔️** | **✔️** | +| 启用项目板 | | | | **✔️** | **✔️** | +| 配置[拉取请求合并](/articles/configuring-pull-request-merges) | | | | **✔️** | **✔️** | +| 配置[ {% data variables.product.prodname_pages %} 的发布源](/articles/configuring-a-publishing-source-for-github-pages) | | | | **✔️** | **✔️** | +| [管理分支保护规则](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **✔️** | +| [推送到受保护分支](/articles/about-protected-branches) | | | | **✔️** | **✔️** | +| 合并受保护分支上的拉取请求（即使没有批准审查） | | | | | **✔️** |{% ifversion fpt or ghes > 3.4 or ghae-issue-6337 or ghec %} +| 创建与[标记保护规则](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)匹配的标记 | | | | **✔️** | **✔️** | +| 删除与[标记保护规则](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)匹配的标记 | | | | | **✔️** {% endif %} -| [创建和编辑仓库社交卡](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt or ghec %} -| 限制[仓库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **X** | **X** +| [创建和编辑仓库社交卡](/articles/customizing-your-repositorys-social-media-preview) | | | | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| 限制[仓库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **✔️** | **✔️** {% endif %} -| 删除议题（请参阅“[删除议题](/articles/deleting-an-issue)”） | | | | | **X** | -| [定义仓库的代码所有者](/articles/about-code-owners) | | | | | **X** | -| 将仓库添加到团队（详细信息请参阅“[管理团队对组织仓库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)”） | | | | | **X** | -| [管理外部协作者对仓库的权限](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [更改仓库的可见性](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| 将仓库设为模板（请参阅“[创建模板仓库](/articles/creating-a-template-repository)”） | | | | | **X** | -| 更改仓库设置 | | | | | **X** | -| 管理团队和协作者对仓库的权限 | | | | | **X** | -| 编辑仓库的默认分支 | | | | | **X** | -| 重命名仓库的默认分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”） | | | | | **X** | -| 重命名仓库默认分支以外的分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”） | | | **X** | **X** | **X** | -| 管理 web 挂钩和部署密钥 | | | | | **X** |{% ifversion fpt or ghec %} -| [管理私有仓库的数据使用设置](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository) | | | | | **X** +| 删除议题（请参阅“[删除议题](/articles/deleting-an-issue)”） | | | | | **✔️** | +| [定义仓库的代码所有者](/articles/about-code-owners) | | | | | **✔️** | +| 将仓库添加到团队（详细信息请参阅“[管理团队对组织仓库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)”） | | | | | **✔️** | +| [管理外部协作者对仓库的权限](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **✔️** | +| [更改仓库的可见性](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **✔️** | +| 将仓库设为模板（请参阅“[创建模板仓库](/articles/creating-a-template-repository)”） | | | | | **✔️** | +| 更改仓库设置 | | | | | **✔️** | +| 管理团队和协作者对仓库的权限 | | | | | **✔️** | +| 编辑仓库的默认分支 | | | | | **✔️** | +| 重命名仓库的默认分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”） | | | | | **✔️** | +| 重命名仓库默认分支以外的分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”） | | | **✔️** | **✔️** | **✔️** | +| 管理 web 挂钩和部署密钥 | | | | | **✔️** |{% ifversion fpt or ghec %} +| [管理私有仓库的数据使用设置](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository) | | | | | **✔️** {% endif %} -| [管理仓库的复刻策略](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [将仓库转让给组织](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [删除仓库或将仓库转让到组织外部](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [存档仓库](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt or ghec %} -| 显示赞助按钮（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）。 | | | | | **X** +| [管理仓库的复刻策略](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **✔️** | +| [将仓库转让给组织](/articles/restricting-repository-creation-in-your-organization) | | | | | **✔️** | +| [删除仓库或将仓库转让到组织外部](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **✔️** | +| [存档仓库](/articles/about-archiving-repositories) | | | | | **✔️** |{% ifversion fpt or ghec %} +| 显示赞助按钮（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）。 | | | | | **✔️** {% endif %} -| 创建到外部资源的自动链接引用，如 Jira 或 Zendesk（请参阅“[配置自动链接以引用外部资源](/articles/configuring-autolinks-to-reference-external-resources)”） | | | | | **X** |{% ifversion discussions %} -| 在仓库中[启用 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) | | | | **X** | **X** | -| 为 {% data variables.product.prodname_discussions %} [创建和编辑类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) | | | | **X** | **X** | -| [将讨论移动到其他类别](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [将讨论转移到](/discussions/managing-discussions-for-your-community/managing-discussions)新仓库 | | | **X** | **X** | **X** | -| [管理置顶的讨论](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [批量将议题转换为讨论](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [锁定和解锁讨论](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [单独将议题转换为讨论](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [创建新的讨论并对现有讨论发表评论](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | -| [删除讨论](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **X** | | **X** | **X** |{% endif %}{% ifversion fpt or ghec %} -| 创建 [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** +| 创建到外部资源的自动链接引用，如 Jira 或 Zendesk（请参阅“[配置自动链接以引用外部资源](/articles/configuring-autolinks-to-reference-external-resources)”） | | | | | **✔️** |{% ifversion discussions %} +| 在仓库中[启用 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) | | | | **✔️** | **✔️** | +| 为 {% data variables.product.prodname_discussions %} [创建和编辑类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) | | | | **✔️** | **✔️** | +| [将讨论移动到其他类别](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [将讨论转移到](/discussions/managing-discussions-for-your-community/managing-discussions)新仓库 | | | **✔️** | **✔️** | **✔️** | +| [管理置顶的讨论](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [批量将议题转换为讨论](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [锁定和解锁讨论](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | +| [单独将议题转换为讨论](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | +| [创建新的讨论并对现有讨论发表评论](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [删除讨论](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **✔️** | | **✔️** | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| 创建 [codespaces](/codespaces/about-codespaces) | | | **✔️** | **✔️** | **✔️** {% endif %} ### 安全功能的访问要求 在本节中，您可以找到一些安全功能所需的访问权限，例如 {% data variables.product.prodname_advanced_security %} 功能。 -| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 | -|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------:| -| 接收仓库中[非安全依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) | | | | | **X** | -| [忽略 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% ifversion ghes or ghae or ghec %} +| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 | +|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------:|:------:|:-------------------------------------------------------:|:-------------------------------------------------------:|:--------------------------------------------------------------------------------------------------:| +| 接收仓库中[非安全依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) | | | | | **✔️** | +| [忽略 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **✔️** |{% ifversion ghes or ghae or ghec %} | -| [指定其他人员或团队接收安全警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} -| 创建[安全通告](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [指定其他人员或团队接收安全警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| 创建[安全通告](/code-security/security-advisories/about-github-security-advisories) | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} | -| 管理 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限（请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”） | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} +| 管理 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限（请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”） | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} | -| 为私有仓库[启用依赖关系图](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} -| [查看依赖项审查](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** +| 为私有仓库[启用依赖关系图](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [查看依赖项审查](/code-security/supply-chain-security/about-dependency-review) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** {% endif %} -| [查看拉取请求上的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | -| [列出、忽略和删除 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | -| [查看仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} +| [查看拉取请求上的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [列出、忽略和删除 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **✔️** | **✔️** | **✔️** | +| [查看仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% ifversion ghes or ghae or ghec %} | -| [解决、撤销或重新打开 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} -| [指定其他人员或团队接收仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** +| [解决、撤销或重新打开 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [指定其他人员或团队接收仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **✔️** {% endif %} [1] 仓库作者和维护者只能看到他们自己提交的警报信息。 diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index a8fea4e9e3..0b95f8dda4 100644 --- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -12,14 +12,12 @@ topics: shortTitle: 使用 SAML SSO 的 IAM --- -{% data reusables.enterprise-accounts.emu-saml-note %} +{% data reusables.saml.ghec-only %} ## 关于 SAML SSO {% data reusables.saml.dotcom-saml-explanation %} -{% data reusables.saml.ghec-only %} - {% data reusables.saml.saml-accounts %} 组织所有者可以对单个组织强制实施 SAML SSO，企业所有者可以为企业帐户中的所有组织强制实施 SAML SSO。 更多信息请参阅“[配置企业的 SAML 单点登录](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)”。 diff --git a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md index 215c4a2267..f513de90b9 100644 --- a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md +++ b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md @@ -18,6 +18,8 @@ shortTitle: 验证自定义域 验证域时，验证中还会包含任何直接子域。 例如，如果 `github.com` 自定义域经过验证，则 `docs.github.com`、`support.github.com` 和任何其他直接子域也将受到保护，以防止被接管。 +{% data reusables.pages.wildcard-dns-warning %} + 还可以验证组织{% ifversion ghec %} 或企业{% endif %}的域，这会在组织 {% ifversion ghec %}或企业{% endif %} 配置文件{% ifversion ghec %} 以及 {% data variables.product.prodname_ghe_cloud %} 上显示“已验证”徽章，允许您使用已验证的域将通知限于电子邮件地址{% endif %}。 更多信息请参阅“[验证或批准组织的域](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization){% ifversion ghec %}”和“[验证或批准企业的域](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% endif %}”。 ## 验证用户站点的域 diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md index 765d90a90f..d270178440 100644 --- a/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -126,6 +126,7 @@ In addition, your use of {% data variables.product.prodname_pages %} is subject {% ifversion fpt or ghec %} - {% data variables.product.prodname_pages %} sites have a *soft* bandwidth limit of 100 GB per month. - {% data variables.product.prodname_pages %} sites have a *soft* limit of 10 builds per hour.{% ifversion pages-custom-workflow %} This limit does not apply if you build and publish your site with a custom {% data variables.product.prodname_actions %} workflow {% endif %} + - In order to provide consistent quality of service for all {% data variables.product.prodname_pages %} sites, rate limits may apply. These rate limits are not intended to interfere with legitimate uses of {% data variables.product.prodname_pages %}. If your request triggers rate limiting, you will receive an appropriate response with an HTTP status code of `429`, along with an informative HTML body. If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from {% data variables.contact.contact_support %} suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other {% data variables.product.prodname_dotcom %} features such as releases, or moving to a different hosting service that might better fit your needs. diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md index e4699a8b26..49eeb95f5f 100644 --- a/translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -46,17 +46,11 @@ shortTitle: 配置发布源 如果选择任意分支上的 `docs` 文件夹作为发布源，然后从仓库的该分支中删除了 `/docs` 文件夹，则您的站点将不会构建，并且您将收到提示缺失 `/docs` 文件夹的页面构建错误。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误疑难排解](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)”。 -{% ifversion fpt %} +{% ifversion build-pages-with-actions %} {% data variables.product.prodname_pages %} 站点将始终使用 {% data variables.product.prodname_actions %} 工作流程运行进行部署，即使您已将 {% data variables.product.prodname_pages %} 站点配置为使用其他 CI 工具构建也是如此。 大多数外部 CI 工作流程通过将构建输出提交到仓库的 `gh-pages` 分支来“部署”到 GitHub Pages，并且通常包含一个 `.nojekyll` 文件。 发生这种情况时， {% data variables.product.prodname_actions %} 工作流程将检测分支不需要构建步骤的状态，并且仅执行将站点部署到 {% data variables.product.prodname_pages %} 服务器所需的步骤。 -若要查找构建或部署的潜在错误，可以通过查看仓库的工作流程运行来检查 {% data variables.product.prodname_pages %} 站点的工作流程运行情况。 更多信息请参阅“[查看工作流程运行历史记录](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)”。 有关如何在出现错误时重新运行工作流程的详细信息，请参阅”[重新运行工作流程和作业](/actions/managing-workflow-runs/re-running-workflows-and-jobs)“。 - -{% note %} - -{% data reusables.pages.pages-builds-with-github-actions-public-beta %} - -{% endnote %} +若要查找构建或部署的潜在错误，可以通过查看仓库的工作流程运行来检查 {% data variables.product.prodname_pages %} 站点的工作流程运行情况。 更多信息请参阅“[查看工作流程运行历史记录](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)”。 有关如何在出现错误时重新运行工作流程的详细信息，请参阅”[重新运行工作流程和作业](/actions/managing-workflow-runs/re-running-workflows-and-jobs)“。 {% endif %} diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md index b76538436f..9e84172aa2 100644 --- a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -30,26 +30,27 @@ shortTitle: Jekyll build errors for Pages {% endnote %} +{% ifversion build-pages-with-actions %} +If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. +{% else %} If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. There are two main types of Jekyll build error messages. - A "Page build warning" message means your build completed successfully, but you may need to make changes to prevent future problems. - A "Page build failed" message means your build failed to complete. If Jekyll is able to detect a reason for the failure, you'll see a descriptive error message. +{% endif %} For more information about troubleshooting build errors, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)." -{% ifversion fpt %} +{% ifversion build-pages-with-actions %} ## Viewing Jekyll build error messages with {% data variables.product.prodname_actions %} By default, your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. To find potential build errors, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." -{% note %} - -{% data reusables.pages.pages-builds-with-github-actions-public-beta %} - -{% endnote %} {% endif %} +{% ifversion build-pages-with-actions %}{% else %} ## Viewing your repository's build failures on {% data variables.product.product_name %} You can see build failures (but not build warnings) for your site on {% data variables.product.product_name %} in the **Settings** tab of your site's repository. +{% endif %} ## Viewing Jekyll build error messages locally @@ -63,7 +64,7 @@ We recommend testing your site locally, which allows you to see build error mess ## Viewing Jekyll build errors by email -{% ifversion pages-custom-workflow %}If you are publishing from a branch, when{% else %}When{% endif %} you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. You'll also receive emails for build warnings. {% data reusables.pages.build-failure-email-server %} +{% ifversion pages-custom-workflow %}If you are publishing from a branch, when{% else %}When{% endif %} you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. {% data reusables.pages.build-failure-email-server %} {% ifversion pages-custom-workflow %}If you are publishing with a custom {% data variables.product.prodname_actions %} workflow, in order to receive emails about build errors in your pull request, you must configure your workflow to run on the `pull_request` trigger. When you do this, we recommend that you skip any deploy steps if the workflow was triggered by the `pull_request` event. This will allow you to see any build errors without deploying the changes from your pull request to your site. For more information, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows#pull_request)" and "[Expressions](/actions/learn-github-actions/expressions)."{% endif %} diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md index 44d95b6bac..8f5c95398f 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -25,6 +25,7 @@ shortTitle: 创建和删除分支 {% endnote %} +{% ifversion create-branch-from-overview %} ### 通过分支概述创建分支 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-branches %} @@ -32,16 +33,19 @@ shortTitle: 创建和删除分支 2. 在对话框中，输入分支名称，并根据需要更改分支源。 如果存储库是复刻，您还可以选择上游存储库作为分支源。 ![强调分支源的复刻的分支创建模式屏幕截图](/assets/images/help/branches/branch-creation-popup-branch-source.png) 3. 单击 **Create Branch（创建分支）**。 ![突出显示了创建分支按钮的分支创建模式的屏幕截图](/assets/images/help/branches/branch-creation-popup-button.png) +{% endif %} ### 使用分支下拉列表创建分支 {% data reusables.repositories.navigate-to-repo %} 1. （可选）如果要从仓库的默认分支以外的分支创建新分支，请单击 {% octicon "git-branch" aria-label="The branch icon" %}**Branches（分支）**，然后选择另一个分支。 ![概述页面上的分支链接](/assets/images/help/branches/branches-overview-link.png) 1. 单击分支选择器菜单。 ![分支选择器菜单](/assets/images/help/branch/branch-selection-dropdown.png) 1. 为新分支键入唯一名称，然后选择 **Create branch（创建分支）**。 ![分支创建文本框](/assets/images/help/branch/branch-creation-text-box.png) + {% ifversion fpt or ghec or ghes > 3.4 %} ### 为议题创建分支 您可以创建一个分支，直接从议题页面处理议题，然后立即开始。 更多信息请参阅“[创建分支以处理议题](/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue)”。 {% endif %} + ## 删除分支 {% data reusables.pull_requests.automatically-delete-branches %} diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md index 5233724548..70c5d69927 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md @@ -23,9 +23,14 @@ permissions: People with write access for a forked repository can sync the fork ## 从 web UI 同步复刻分支 +{% ifversion syncing-fork-web-ui %} 1. 在 {% data variables.product.product_name %} 上，导航到您想要与上游版本库同步的复刻仓库主页。 -2. 选择 **Fetch upstream（提取上游）**下拉菜单。 !["Fetch upstream（提取上游）"下拉菜单](/assets/images/help/repository/fetch-upstream-drop-down.png) -3. 查看上游仓库中有关提交的细节，然后单击“**提取并合并**”。 !["提取并合并"按钮](/assets/images/help/repository/fetch-and-merge-button.png) +2. Select the **Sync fork** dropdown. !["Sync fork" dropdown emphasized](/assets/images/help/repository/sync-fork-dropdown.png) +3. Review the details about the commits from the upstream repository, then click **Update branch**. ![Sync fork modal with "Update branch" button emphasized](/assets/images/help/repository/update-branch-button.png) +{% else %} +1. 在 {% data variables.product.product_name %} 上，导航到您想要与上游版本库同步的复刻仓库主页。 +2. Select the **Fetch upstream** dropdown. !["Fetch upstream（提取上游）"下拉菜单](/assets/images/help/repository/fetch-upstream-drop-down.png) +3. 查看上游仓库中有关提交的细节，然后单击“**提取并合并**”。 !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} 如果上游仓库的更改导致冲突，{% data variables.product.company_short %} 将提示您创建拉取请求以解决冲突。 diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md b/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md index 6b12b513ff..12c893cf16 100644 --- a/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md @@ -91,7 +91,7 @@ shortTitle: 搜索仓库 | 限定符 | 示例 | | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) 匹配恰好具有 500 个星号的仓库。 | -| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) 匹配具有 10 到 20 个星号、小于 1000 KB 的仓库。 | +| | [**stars:10..20 size:<1000**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB. | | | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) 匹配具有至少 500 个星号，包括复刻的星号（以 PHP 编写）的仓库。 | ## 按仓库创建或上次更新时间搜索 diff --git a/translations/zh-CN/data/features/build-pages-with-actions.yml b/translations/zh-CN/data/features/build-pages-with-actions.yml new file mode 100644 index 0000000000..0e80ab5a21 --- /dev/null +++ b/translations/zh-CN/data/features/build-pages-with-actions.yml @@ -0,0 +1,5 @@ +#Issue 7584 +#Building Pages sites with Actions [GA] +versions: + fpt: '*' + ghec: '*' diff --git a/translations/zh-CN/data/features/create-branch-from-overview.yml b/translations/zh-CN/data/features/create-branch-from-overview.yml new file mode 100644 index 0000000000..a51e624c41 --- /dev/null +++ b/translations/zh-CN/data/features/create-branch-from-overview.yml @@ -0,0 +1,5 @@ +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.7' + ghae: 'issue-6670' diff --git a/translations/zh-CN/data/features/security-overview-displayed-alerts.yml b/translations/zh-CN/data/features/security-overview-displayed-alerts.yml new file mode 100644 index 0000000000..da84d07e41 --- /dev/null +++ b/translations/zh-CN/data/features/security-overview-displayed-alerts.yml @@ -0,0 +1,6 @@ +#Reference: #7114. +#Documentation for security overview availability to all enterprise accounts. +versions: + ghec: '*' + ghes: '>=3.7' + ghae: 'issue-7114' diff --git a/translations/zh-CN/data/features/syncing-fork-web-ui.yml b/translations/zh-CN/data/features/syncing-fork-web-ui.yml new file mode 100644 index 0000000000..72bf3f5878 --- /dev/null +++ b/translations/zh-CN/data/features/syncing-fork-web-ui.yml @@ -0,0 +1,7 @@ +#Issue 7629 +#Improved UI for manually syncing a fork +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.7' + ghae: 'issue-7629' diff --git a/translations/zh-CN/data/features/totp-and-mobile-sudo-challenge.yml b/translations/zh-CN/data/features/totp-and-mobile-sudo-challenge.yml index 0eae9cda9c..f32fb6b9ee 100644 --- a/translations/zh-CN/data/features/totp-and-mobile-sudo-challenge.yml +++ b/translations/zh-CN/data/features/totp-and-mobile-sudo-challenge.yml @@ -1,5 +1,5 @@ #TOTP and mobile challenge for sudo mode prompt. versions: - fpt: '*' - ghec: '*' + #fpt: '*' + #ghec: '*' ghes: '>= 3.7' diff --git a/translations/zh-CN/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml b/translations/zh-CN/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml index 22604b42bb..862699bc95 100644 --- a/translations/zh-CN/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml +++ b/translations/zh-CN/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml @@ -114,42 +114,49 @@ upcoming_changes: owner: lukewar - location: ProjectNextFieldType.LINKED_PULL_REQUESTS - description: '`LINKED_PULL_REQUESTS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“LINKED_PULL_REQUESTS”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextFieldType.MILESTONE - description: '`MILESTONE` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“MILESTONE”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextFieldType.NUMBER - description: '`NUMBER` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“NUMBER”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextFieldType.REPOSITORY - description: '`REPOSITORY` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“REPOSITORY”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextFieldType.REVIEWERS - description: '`REVIEWERS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“REVIEWERS”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextFieldType.SINGLE_SELECT - description: '`SINGLE_SELECT` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“SINGLE_SELECT”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' + reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' + date: '2022-10-01T00:00:00+00:00' + criticality: 重大 + owner: lukewar + - + location: ProjectNextFieldType.TASKS + description: '`TASKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 @@ -163,14 +170,7 @@ upcoming_changes: owner: lukewar - location: ProjectNextFieldType.TITLE - description: '`TITLE` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' - reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' - date: '2022-10-01T00:00:00+00:00' - criticality: 重大 - owner: lukewar - - - location: ProjectNextFieldType.TRACKS - description: '`TRACKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“TITLE”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 @@ -178,21 +178,21 @@ upcoming_changes: - location: RemovePullRequestFromMergeQueueInput.branch description: '`branch` 将被删除。' - reason: PRs are removed from the merge queue for the base branch, the `branch` argument is now a no-op + reason: PR 将从基本分支的合并队列中删除，`branch` 参数现在是 no-op date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: jhunschejones - location: RepositoryVulnerabilityAlert.fixReason - description: '`fixReason` will be removed.' - reason: The `fixReason` field is being removed. You can still use `fixedAt` and `dismissReason`. + description: '`fixReason` 将被删除。' + reason: '“fixReason”字段将被删除。您仍可使用“fixedAt”和“dismissReson”。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: jamestran201 - location: UnlockAndResetMergeGroupInput.branch description: '`branch` 将被删除。' - reason: The current merge group for the repository's default branch, the `branch` argument is now a no-op + reason: 存储库默认分支的当前合并组，“branch”参数现在是 no-op date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: jhunschejones diff --git a/translations/zh-CN/data/graphql/ghec/graphql_upcoming_changes.public.yml b/translations/zh-CN/data/graphql/ghec/graphql_upcoming_changes.public.yml index 5909c11c92..74549f78c1 100644 --- a/translations/zh-CN/data/graphql/ghec/graphql_upcoming_changes.public.yml +++ b/translations/zh-CN/data/graphql/ghec/graphql_upcoming_changes.public.yml @@ -534,42 +534,49 @@ upcoming_changes: owner: lukewar - location: ProjectNextFieldType.LINKED_PULL_REQUESTS - description: '`LINKED_PULL_REQUESTS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“LINKED_PULL_REQUESTS”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextFieldType.MILESTONE - description: '`MILESTONE` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“MILESTONE”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextFieldType.NUMBER - description: '`NUMBER` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“NUMBER”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextFieldType.REPOSITORY - description: '`REPOSITORY` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“REPOSITORY”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextFieldType.REVIEWERS - description: '`REVIEWERS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“REVIEWERS”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextFieldType.SINGLE_SELECT - description: '`SINGLE_SELECT` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“SINGLE_SELECT”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' + reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' + date: '2022-10-01T00:00:00+00:00' + criticality: 重大 + owner: lukewar + - + location: ProjectNextFieldType.TASKS + description: '`TASKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 @@ -583,14 +590,7 @@ upcoming_changes: owner: lukewar - location: ProjectNextFieldType.TITLE - description: '`TITLE` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' - reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' - date: '2022-10-01T00:00:00+00:00' - criticality: 重大 - owner: lukewar - - - location: ProjectNextFieldType.TRACKS - description: '`TRACKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“TITLE”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 @@ -849,14 +849,14 @@ upcoming_changes: owner: lukewar - location: ProjectNextOrderField.NUMBER - description: '`NUMBER` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“NUMBER”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextOrderField.TITLE - description: '`TITLE` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“TITLE”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 @@ -1081,7 +1081,7 @@ upcoming_changes: - location: RemovePullRequestFromMergeQueueInput.branch description: '`branch` 将被删除。' - reason: PRs are removed from the merge queue for the base branch, the `branch` argument is now a no-op + reason: PR 将从基本分支的合并队列中删除，`branch` 参数现在是 no-op date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: jhunschejones @@ -1108,15 +1108,15 @@ upcoming_changes: owner: lukewar - location: RepositoryVulnerabilityAlert.fixReason - description: '`fixReason` will be removed.' - reason: The `fixReason` field is being removed. You can still use `fixedAt` and `dismissReason`. + description: '`fixReason` 将被删除。' + reason: '“fixReason”字段将被删除。您仍可使用“fixedAt”和“dismissReson”。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: jamestran201 - location: UnlockAndResetMergeGroupInput.branch description: '`branch` 将被删除。' - reason: The current merge group for the repository's default branch, the `branch` argument is now a no-op + reason: 存储库默认分支的当前合并组，“branch”参数现在是 no-op date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: jhunschejones diff --git a/translations/zh-CN/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml b/translations/zh-CN/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml index 6a780f3a4d..df29a6761f 100644 --- a/translations/zh-CN/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml +++ b/translations/zh-CN/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml @@ -80,7 +80,7 @@ upcoming_changes: - location: RemovePullRequestFromMergeQueueInput.branch description: '`branch` 将被删除。' - reason: PRs are removed from the merge queue for the base branch, the `branch` argument is now a no-op + reason: PR 将从基本分支的合并队列中删除，`branch` 参数现在是 no-op date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: jhunschejones diff --git a/translations/zh-CN/data/graphql/graphql_upcoming_changes.public.yml b/translations/zh-CN/data/graphql/graphql_upcoming_changes.public.yml index 5909c11c92..74549f78c1 100644 --- a/translations/zh-CN/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/zh-CN/data/graphql/graphql_upcoming_changes.public.yml @@ -534,42 +534,49 @@ upcoming_changes: owner: lukewar - location: ProjectNextFieldType.LINKED_PULL_REQUESTS - description: '`LINKED_PULL_REQUESTS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“LINKED_PULL_REQUESTS”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextFieldType.MILESTONE - description: '`MILESTONE` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“MILESTONE”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextFieldType.NUMBER - description: '`NUMBER` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“NUMBER”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextFieldType.REPOSITORY - description: '`REPOSITORY` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“REPOSITORY”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextFieldType.REVIEWERS - description: '`REVIEWERS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“REVIEWERS”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextFieldType.SINGLE_SELECT - description: '`SINGLE_SELECT` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“SINGLE_SELECT”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' + reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' + date: '2022-10-01T00:00:00+00:00' + criticality: 重大 + owner: lukewar + - + location: ProjectNextFieldType.TASKS + description: '`TASKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 @@ -583,14 +590,7 @@ upcoming_changes: owner: lukewar - location: ProjectNextFieldType.TITLE - description: '`TITLE` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' - reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' - date: '2022-10-01T00:00:00+00:00' - criticality: 重大 - owner: lukewar - - - location: ProjectNextFieldType.TRACKS - description: '`TRACKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“TITLE”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 @@ -849,14 +849,14 @@ upcoming_changes: owner: lukewar - location: ProjectNextOrderField.NUMBER - description: '`NUMBER` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“NUMBER”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: lukewar - location: ProjectNextOrderField.TITLE - description: '`TITLE` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + description: '“TITLE”将被删除。请按照 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ 的 ProjectV2 指南，找到合适的替代项。' reason: '''ProjectNext'' API 已被弃用，取而代之的是功能更强大的 ''ProjectV2'' API。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 @@ -1081,7 +1081,7 @@ upcoming_changes: - location: RemovePullRequestFromMergeQueueInput.branch description: '`branch` 将被删除。' - reason: PRs are removed from the merge queue for the base branch, the `branch` argument is now a no-op + reason: PR 将从基本分支的合并队列中删除，`branch` 参数现在是 no-op date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: jhunschejones @@ -1108,15 +1108,15 @@ upcoming_changes: owner: lukewar - location: RepositoryVulnerabilityAlert.fixReason - description: '`fixReason` will be removed.' - reason: The `fixReason` field is being removed. You can still use `fixedAt` and `dismissReason`. + description: '`fixReason` 将被删除。' + reason: '“fixReason”字段将被删除。您仍可使用“fixedAt”和“dismissReson”。' date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: jamestran201 - location: UnlockAndResetMergeGroupInput.branch description: '`branch` 将被删除。' - reason: The current merge group for the repository's default branch, the `branch` argument is now a no-op + reason: 存储库默认分支的当前合并组，“branch”参数现在是 no-op date: '2022-10-01T00:00:00+00:00' criticality: 重大 owner: jhunschejones diff --git a/translations/zh-CN/data/reusables/actions/jobs/multi-dimension-matrix.md b/translations/zh-CN/data/reusables/actions/jobs/multi-dimension-matrix.md index 7ab7b33286..a15ce70b88 100644 --- a/translations/zh-CN/data/reusables/actions/jobs/multi-dimension-matrix.md +++ b/translations/zh-CN/data/reusables/actions/jobs/multi-dimension-matrix.md @@ -12,7 +12,7 @@ jobs: example_matrix: strategy: matrix: - os: [ubuntu-18.04, ubuntu-20.04] + os: [ubuntu-22.04, ubuntu-20.04] version: [10, 12, 14] runs-on: {% raw %}${{ matrix.os }}{% endraw %} steps: diff --git a/translations/zh-CN/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md b/translations/zh-CN/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md index fc80599a2d..05f5176fbc 100644 --- a/translations/zh-CN/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md +++ b/translations/zh-CN/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md @@ -6,7 +6,7 @@ ### 选择 {% data variables.product.prodname_dotcom %} 托管的运行器 -如果使用 {% data variables.product.prodname_dotcom %} 托管的运行器，每个作业将在 `runs-on` 指定的虚拟环境的新实例中运行。 +If you use a {% data variables.product.prodname_dotcom %}-hosted runner, each job runs in a fresh instance of a runner image specified by `runs-on`. 可用的 {% data variables.product.prodname_dotcom %} 托管的运行器类型包括： @@ -18,7 +18,7 @@ runs-on: ubuntu-latest ``` -更多信息请参阅“[{% data variables.product.prodname_dotcom %} 托管的运行器的虚拟环境](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)”。 +更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 托管的运行器](/actions/using-github-hosted-runners/about-github-hosted-runners)”。 {% endif %} {% ifversion fpt or ghec or ghes %} diff --git a/translations/zh-CN/data/reusables/actions/macos-runner-preview.md b/translations/zh-CN/data/reusables/actions/macos-runner-preview.md index 1f4d6b516e..c9b93aecbe 100644 --- a/translations/zh-CN/data/reusables/actions/macos-runner-preview.md +++ b/translations/zh-CN/data/reusables/actions/macos-runner-preview.md @@ -1 +1 @@ -macos-latest YAML 工作流程标签目前使用 MacOS 10.15 虚拟环境。 +The macos-latest YAML workflow label currently uses the macOS 10.15 runner image. diff --git a/translations/zh-CN/data/reusables/actions/pure-javascript.md b/translations/zh-CN/data/reusables/actions/pure-javascript.md index a964113df9..1086503850 100644 --- a/translations/zh-CN/data/reusables/actions/pure-javascript.md +++ b/translations/zh-CN/data/reusables/actions/pure-javascript.md @@ -1 +1 @@ -要确保您的 JavaScript 操作与所有 GitHub 托管的运行器（Ubuntu、Windows 和 macOS）兼容，您编写的封装 JavaScript 代码应该是纯粹的 JavaScript，不能依赖于其他二进制文件。 JavaScript 操作直接在运行器上运行，并使用虚拟环境中已存在的二进制文件。 +要确保您的 JavaScript 操作与所有 GitHub 托管的运行器（Ubuntu、Windows 和 macOS）兼容，您编写的封装 JavaScript 代码应该是纯粹的 JavaScript，不能依赖于其他二进制文件。 JavaScript actions run directly on the runner and use binaries that already exist in the runner image. diff --git a/translations/zh-CN/data/reusables/actions/supported-github-runners.md b/translations/zh-CN/data/reusables/actions/supported-github-runners.md index 5b8a5bb064..80b1f80fe9 100644 --- a/translations/zh-CN/data/reusables/actions/supported-github-runners.md +++ b/translations/zh-CN/data/reusables/actions/supported-github-runners.md @@ -1,7 +1,7 @@
仮想環境Runner image YAMLのワークフローラベル 注釈
- + @@ -36,7 +36,6 @@ Ubuntu 22.04 ubuntu-22.04 @@ -49,12 +48,13 @@ Ubuntu 20.04 @@ -92,7 +92,7 @@ Migrate to macOS-11 or macOS-12. For more information, {% note %} -**注意：** `-latest` 虚拟环境是 {% data variables.product.prodname_dotcom %} 提供的最新稳定映像，可能不是操作系统供应商提供的最新版本的操作系统。 +**Note:** The `-latest` runner images are the latest stable images that {% data variables.product.prodname_dotcom %} provides, and might not be the most recent version of the operating system available from the operating system vendor. {% endnote %} diff --git a/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md index ee1fbbee0b..ecaa7e9b83 100644 --- a/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md +++ b/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md @@ -19,7 +19,11 @@ ![搜索分支以创建新的 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) -5. 单击您要使用的机器类型。 +5. If prompted to choose a dev container configuration file, choose a file from the list. + + ![Choosing a dev container configuration file for {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-dev-container-vscode.png) + +6. 单击您要使用的机器类型。 ![新 {% data variables.product.prodname_codespaces %} 的实例类型](/assets/images/help/codespaces/choose-sku-vscode.png) diff --git a/translations/zh-CN/data/reusables/gated-features/advanced-security.md b/translations/zh-CN/data/reusables/gated-features/advanced-security.md deleted file mode 100644 index b6516c2a85..0000000000 --- a/translations/zh-CN/data/reusables/gated-features/advanced-security.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_GH_advanced_security %} 是一组安全功能，旨在使企业代码更安全。 它可用于 {% data variables.product.prodname_ghe_server %} 3.0 或更高版本、 {% data variables.product.prodname_ghe_cloud %} 和开源存储库。 要了解有关 {% data variables.product.prodname_GH_advanced_security %} 中包含的功能的更多信息，请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)”。 diff --git a/translations/zh-CN/data/reusables/gated-features/environments.md b/translations/zh-CN/data/reusables/gated-features/environments.md index 6ccb15e462..cc73186b18 100644 --- a/translations/zh-CN/data/reusables/gated-features/environments.md +++ b/translations/zh-CN/data/reusables/gated-features/environments.md @@ -1 +1 @@ -所有产品的**公共**仓库提供环境、环境保护规则和环境机密。 要访问**私人**仓库的环境，您必须使用 {% data variables.product.prodname_enterprise %}。 {% data reusables.gated-features.more-info %} +所有产品的**公共**仓库提供环境、环境保护规则和环境机密。 For access to environments in **private** or **internal** repositories, you must use {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info %} diff --git a/translations/zh-CN/data/reusables/gated-features/ghas.md b/translations/zh-CN/data/reusables/gated-features/ghas.md index deb8f173c0..ea2eb23626 100644 --- a/translations/zh-CN/data/reusables/gated-features/ghas.md +++ b/translations/zh-CN/data/reusables/gated-features/ghas.md @@ -1 +1 @@ -{% data variables.product.prodname_GH_advanced_security %} 适用于 {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}、{% data variables.product.prodname_ghe_managed %}，{% endif %} 和 {% data variables.product.prodname_ghe_server %} 3.0 或更高版本上的企业帐户。{% ifversion fpt or ghec %} {% data variables.product.prodname_GH_advanced_security %} 也包含在 {% data variables.product.prodname_dotcom_the_website %} 上的所有公共仓库中。 更多信息请参阅“[关于 GitHub 的产品](/github/getting-started-with-github/githubs-products)”。{% else %} 有关升级 {% data variables.product.prodname_ghe_server %} 实例的更多信息，请参阅“[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)”，并参阅 [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) 以查找当前发行版的升级路径。{% endif %} +{% data variables.product.prodname_GH_advanced_security %} is available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}.{% ifversion fpt or ghec %} Some features of {% data variables.product.prodname_GH_advanced_security %} are also available for public repositories on {% data variables.product.prodname_dotcom_the_website %}. 更多信息请参阅“[关于 GitHub 的产品](/github/getting-started-with-github/githubs-products)”。{% else %} 有关升级 {% data variables.product.prodname_ghe_server %} 实例的更多信息，请参阅“[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)”，并参阅 [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) 以查找当前发行版的升级路径。{% endif %} diff --git a/translations/zh-CN/data/reusables/gated-features/security-overview.md b/translations/zh-CN/data/reusables/gated-features/security-overview.md index c50d6b246b..3aeba0cb69 100644 --- a/translations/zh-CN/data/reusables/gated-features/security-overview.md +++ b/translations/zh-CN/data/reusables/gated-features/security-overview.md @@ -1,6 +1,9 @@ -{% ifversion ghae %} -如果您有 {% data variables.product.prodname_GH_advanced_security %} 许可证，则可获得组织的安全概览，该许可证在测试版期间是免费的。 {% data reusables.advanced-security.more-info-ghas %} -{% elsif ghec or ghes %} +{% ifversion fpt %} +The security overview is available for organizations that use {% data variables.product.prodname_enterprise %}. 更多信息请参阅“[GitHub's products](/articles/githubs-products)”。 +{% elsif security-overview-displayed-alerts %} +All organizations and enterprises have a security overview. If you use {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghae %}, which is free during the beta release,{% endif %} you will see additional information. {% data reusables.advanced-security.more-info-ghas %} +{% elsif ghes < 3.7 %} 组织的安全概览在您拥有 {% data variables.product.prodname_GH_advanced_security %} 的许可证时可用。 {% data reusables.advanced-security.more-info-ghas %} -{% elsif fpt %} -安全性概述适用于使用 {% data variables.product.prodname_enterprise %} 并拥有 {% data variables.product.prodname_GH_advanced_security %} 许可证的组织。 更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)”。 {% endif %} +{% elsif ghae %} +A security overview for your enterprise and for organizations is available if you use {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release. {% data reusables.advanced-security.more-info-ghas %} +{% endif %} diff --git a/translations/zh-CN/data/reusables/getting-started/math-and-diagrams.md b/translations/zh-CN/data/reusables/getting-started/math-and-diagrams.md new file mode 100644 index 0000000000..0b8fd102b4 --- /dev/null +++ b/translations/zh-CN/data/reusables/getting-started/math-and-diagrams.md @@ -0,0 +1 @@ +{% ifversion mermaid %}You can use Markdown to add rendered math expressions, diagrams, maps, and 3D models to your wiki. For more information on creating rendered math expressions, see "[Writing mathematical expressions](/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions)." For more information on creating diagrams, maps and 3D models, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)."{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/pages/check-workflow-run.md b/translations/zh-CN/data/reusables/pages/check-workflow-run.md index d713613f9f..26730fbe06 100644 --- a/translations/zh-CN/data/reusables/pages/check-workflow-run.md +++ b/translations/zh-CN/data/reusables/pages/check-workflow-run.md @@ -1,8 +1,10 @@ -{% ifversion fpt %} -1. Unless your {% data variables.product.prodname_pages %} site is built from a private or internal repository and published from a branch, your site is built and deployed with a {% data variables.product.prodname_actions %} workflow. 有关如何查看工作流程状态的详细信息，请参阅“[查看工作流程运行历史记录](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)”。 +{% ifversion build-pages-with-actions %} +1. Your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". -{% note %} + {% note %} -{% data reusables.pages.pages-builds-with-github-actions-public-beta %} + **Note:** {% data variables.product.prodname_actions %} is free for public repositories. Usage charges apply for private and internal repositories that go beyond the monthly allotment of free minutes. 更多信息请参阅“[使用限制、计费和管理](/actions/reference/usage-limits-billing-and-administration)”。 -{% endnote %}{% endif %} + {% endnote %} + +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/pages/pages-builds-with-github-actions-public-beta.md b/translations/zh-CN/data/reusables/pages/pages-builds-with-github-actions-public-beta.md deleted file mode 100644 index 0daefdc979..0000000000 --- a/translations/zh-CN/data/reusables/pages/pages-builds-with-github-actions-public-beta.md +++ /dev/null @@ -1,5 +0,0 @@ -{% ifversion fpt %} - -**Note:** {% data variables.product.prodname_actions %} workflow runs for your {% data variables.product.prodname_pages %} sites are in public beta for public repositories and subject to change. {% data variables.product.prodname_actions %} workflow runs are free for public repositories. - -{% endif %} diff --git a/translations/zh-CN/data/reusables/pages/wildcard-dns-warning.md b/translations/zh-CN/data/reusables/pages/wildcard-dns-warning.md index fffdfe9132..8bd929e90c 100644 --- a/translations/zh-CN/data/reusables/pages/wildcard-dns-warning.md +++ b/translations/zh-CN/data/reusables/pages/wildcard-dns-warning.md @@ -1,5 +1,5 @@ {% warning %} -**警告：**我们强烈建议不要使用通配符 DNS 记录，例如 `*.example.com`。 通配符 DNS 记录将允许任何人在您的其中一个子域上托管 {% data variables.product.prodname_pages %} 站点。 +**警告：**我们强烈建议不要使用通配符 DNS 记录，例如 `*.example.com`。 A wildcard DNS record will allow anyone to host a {% data variables.product.prodname_pages %} site at one of your subdomains even when they are verified. 更多信息请参阅“[验证 {% data variables.product.prodname_pages %} 的自定义域](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)”。 {% endwarning %} diff --git a/translations/zh-CN/data/reusables/saml/dotcom-saml-explanation.md b/translations/zh-CN/data/reusables/saml/dotcom-saml-explanation.md index 395db99f57..77bc0e26ce 100644 --- a/translations/zh-CN/data/reusables/saml/dotcom-saml-explanation.md +++ b/translations/zh-CN/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -SAML 单点登录 (SSO) 为使用 {% data variables.product.product_name %} 的组织所有者和企业所有者提供一种控制安全访问仓库、议题和拉取请求等组织资源的方法。 +SAML 单点登录 (SSO) 为使用 {% data variables.product.product_name %} 的组织所有者和企业所有者提供一种控制安全访问仓库、议题和拉取请求等组织资源的方法。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/saml/outside-collaborators-exemption.md b/translations/zh-CN/data/reusables/saml/outside-collaborators-exemption.md index ac02bf4101..850f097e04 100644 --- a/translations/zh-CN/data/reusables/saml/outside-collaborators-exemption.md +++ b/translations/zh-CN/data/reusables/saml/outside-collaborators-exemption.md @@ -1,5 +1,8 @@ {% note %} -**注：**外部协作者无需使用 IdP 进行身份验证即可访问实施 SAML SSO 的组织中的资源。 有关外部协作者的更多信息，请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)”。 +**注意：** + +- SAML authentication is not required for organization members to perform read operations such as viewing, cloning, and forking of public resources. +- SAML authentication is not required for outside collaborators. 有关外部协作者的更多信息，请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)”。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/saml/saml-accounts.md b/translations/zh-CN/data/reusables/saml/saml-accounts.md index 55eb392168..a6828f6aa0 100644 --- a/translations/zh-CN/data/reusables/saml/saml-accounts.md +++ b/translations/zh-CN/data/reusables/saml/saml-accounts.md @@ -1,7 +1,7 @@ -如果配置 SAML SSO， 组织的成员将继续登录到他们在 {% data variables.product.prodname_dotcom_the_website %} 上的个人帐户。 当成员访问组织内使用 SAML SSO 的非公共资源时，{% data variables.product.prodname_dotcom %} 会将该成员重定向到 IdP 进行身份验证。 身份验证成功后，IdP 将该成员重定向回 {% data variables.product.prodname_dotcom %}，然后成员可以访问组织的资源。 +If you configure SAML SSO, members of your organization will continue to sign into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}. When a member accesses non-public resources within your organization, {% data variables.product.prodname_dotcom %} redirects the member to your IdP to authenticate. After successful authentication, your IdP redirects the member back to {% data variables.product.prodname_dotcom %}. 更多信息请参阅“[关于使用 SAML 单点登录进行身份验证](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)”。 {% note %} -**注意**：即使没有有效的 SAML 会话，组织成员也可以对组织拥有的公共资源执行读取操作，例如查看、克隆和复刻。 +**Note:** SAML SSO does not replace the normal sign-in process for {% data variables.product.prodname_dotcom %}. Unless you use {% data variables.product.prodname_emus %}, members will continue to sign into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}, and each personal account will be linked to an external identity in your IdP. -{% endnote %} +{% endnote %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md b/translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md index 36c3c7f1d1..4312d53aa3 100644 --- a/translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md +++ b/translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md @@ -1,44 +1,17 @@ -| 提供者 | 支持的密钥 | 密钥类型 | -| ------------------------- | ------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | -| Adafruit IO | Adafruit IO 密钥 | adafruit_io_key | -| Alibaba Cloud | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_id
alibaba_cloud_access_key_secret | -| Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id
amazon_oauth_client_secret | -| Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key | aws_access_key_id
aws_secret_access_key | -| Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token
aws_temporary_access_key_id
aws_secret_access_key | -| Asana | Asana 个人访问令牌 | asana_personal_access_token | -| Atlassian | Bitbucket 服务器个人访问令牌 | bitbucket_server_personal_access_token | -| Azure | Azure Active Directory 应用程序密钥 | azure_active_directory_application_secret | -| Azure | Redis 访问密钥的 Azure 缓存 | azure_cache_for_redis_access_key | -| Azure | Azure DevOps 个人访问令牌 | azure_devops_personal_access_token | -| Checkout.com | Checkout.com 生产密钥 | checkout_production_secret_key | -| Clojars | Clojars 部署令牌 | clojars_deploy_token | -| Databricks | Databricks 访问令牌 | databricks_access_token | -| DigitalOcean | DigitalOcean 个人访问令牌 | digitalocean_personal_access_token | -| DigitalOcean | DigitalOcean OAuth 令牌 | digitalocean_oauth_token | -| DigitalOcean | DigitalOcean 刷新令牌 | digitalocean_refresh_token | -| DigitalOcean | DigitalOcean 系统令牌 | digitalocean_system_token | -| Discord | Discord 自动程序令牌 | discord_bot_token | -| Doppler | Doppler 个人令牌 | doppler_personal_token | -| Doppler | Doppler 服务令牌 | doppler_service_token | -| Doppler | Doppler CLI 令牌 | doppler_cli_token | -| Doppler | Doppler SCIM 令牌 | doppler_scim_token | -| Doppler | Doppler Audit 令牌 | doppler_audit_token | -| Dropbox | Dropbox 短暂访问令牌 | dropbox_short_lived_access_token | -| Duffel | Duffel Live Access Token | duffel_live_access_token | -| EasyPost | EasyPost 生产 API 密钥 | easypost_production_api_key | -| Flutterwave | Flutterwave Live API 密钥 | flutterwave_live_api_secret_key | -| Fullstory | FullStory API 密钥 | fullstory_api_key | -| GitHub | GitHub 个人访问令牌 | github_personal_access_token | -| GitHub | GitHub OAuth 访问令牌 | github_oauth_access_token | -| GitHub | GitHub 刷新令牌 | github_refresh_token | -| GitHub | GitHub App 安装访问令牌 | github_app_installation_access_token | -| GitHub | GitHub SSH 私钥 | github_ssh_private_key | -| Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id
google_cloud_storage_access_key_secret | -| Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id
google_cloud_storage_access_key_secret | -| Google | Google OAuth Client ID with Google OAuth Client Secret | google_oauth_client_id
google_oauth_client_secret | -| Grafana | Grafana API 密钥 | grafana_api_key | -| Hubspot | Hubspot API 密钥 | hubspot_api_key | -| Intercom | Intercom 访问令牌 | intercom_access_token | +| 提供者 | 支持的密钥 | 密钥类型 | +| ------------------------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | +| Adafruit IO | Adafruit IO 密钥 | adafruit_io_key | +| Alibaba Cloud | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_id
alibaba_cloud_access_key_secret | +| Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id
amazon_oauth_client_secret | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key | aws_access_key_id
aws_secret_access_key | +| Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token
aws_temporary_access_key_id
aws_secret_access_key | +| Asana | Asana 个人访问令牌 | asana_personal_access_token | +| Atlassian | Bitbucket 服务器个人访问令牌 | bitbucket_server_personal_access_token | +| Azure | Azure Active Directory 应用程序密钥 | azure_active_directory_application_secret | +| Azure | Redis 访问密钥的 Azure 缓存 | azure_cache_for_redis_access_key | +| Azure | Azure DevOps 个人访问令牌 | azure_devops_personal_access_token | +{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %} +Azure | Azure Storage Account Key | azure_storage_account_key{% endif %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key Clojars | Clojars Deploy Token | clojars_deploy_token Databricks | Databricks Access Token | databricks_access_token DigitalOcean | DigitalOcean Personal Access Token | digitalocean_personal_access_token DigitalOcean | DigitalOcean OAuth Token | digitalocean_oauth_token DigitalOcean | DigitalOcean Refresh Token | digitalocean_refresh_token DigitalOcean | DigitalOcean System Token | digitalocean_system_token Discord | Discord Bot Token | discord_bot_token Doppler | Doppler Personal Token | doppler_personal_token Doppler | Doppler Service Token | doppler_service_token Doppler | Doppler CLI Token | doppler_cli_token Doppler | Doppler SCIM Token | doppler_scim_token Doppler | Doppler Audit Token | doppler_audit_token Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token Duffel | Duffel Live Access Token | duffel_live_access_token EasyPost | EasyPost Production API Key | easypost_production_api_key Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key Fullstory | FullStory API Key | fullstory_api_key GitHub | GitHub Personal Access Token | github_personal_access_token GitHub | GitHub OAuth Access Token | github_oauth_access_token GitHub | GitHub Refresh Token | github_refresh_token GitHub | GitHub App Installation Access Token | github_app_installation_access_token GitHub | GitHub SSH Private Key | github_ssh_private_key Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id
google_cloud_storage_access_key_secret Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id
google_cloud_storage_access_key_secret Google | Google OAuth Client ID with Google OAuth Client Secret | google_oauth_client_id
google_oauth_client_secret Grafana | Grafana API Key | grafana_api_key Hubspot | Hubspot API Key | hubspot_api_key Intercom | Intercom Access Token | intercom_access_token {%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %} JFrog | JFrog 平台访问令牌 | jfrog_platform_access_token JFrog | JFrog 平台 API 密钥 | jfrog_platform_api_key{% endif %} Ionic | Ionic 个人访问令牌 | ionic_personal_access_token Ionic | Ionic 刷新令牌 | ionic_refresh_token Linear | Linear API 密钥 | linear_api_key Linear | Linear OAuth 访问令牌 | linear_oauth_access_token Midtrans | Midtrans 生产服务器密钥 | midtrans_production_server_key New Relic | New Relic 个人 API 密钥 | new_relic_personal_api_key New Relic | New Relic REST API 密钥 | new_relic_rest_api_key New Relic | New Relic Insights 查询密钥 | new_relic_insights_query_key npm | npm 访问令牌 | npm_access_token NuGet | NuGet API 密钥 | nuget_api_key Onfido | Onfido Live API 令牌 | onfido_live_api_token OpenAI | OpenAI API 密钥 | openai_api_key PlanetScale | PlanetScale 数据库密码 | planetscale_database_password PlanetScale | PlanetScale OAuth 令牌 | planetscale_oauth_token PlanetScale | PlanetScale 服务令牌 | planetscale_service_token Postman | Postman API 密钥 | postman_api_key Proctorio | Proctorio 密钥 | proctorio_secret_key {%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %} diff --git a/translations/zh-CN/data/reusables/security-overview/information-varies-GHAS.md b/translations/zh-CN/data/reusables/security-overview/information-varies-GHAS.md new file mode 100644 index 0000000000..7d642c7fda --- /dev/null +++ b/translations/zh-CN/data/reusables/security-overview/information-varies-GHAS.md @@ -0,0 +1,3 @@ +{% ifversion security-overview-displayed-alerts %} +The information shown in the security overview will vary according to your access to repositories, and on whether {% data variables.product.prodname_GH_advanced_security %} is used by those repositories. +{% endif %} \ No newline at end of file
虚拟环境Runner image YAML 工作流程标签 注：
-Ubuntu 22.04 目前处于公开测试阶段。
-Ubuntu 18.04 +Ubuntu 18.04 [deprecated] ubuntu-18.04 +Migrate to ubuntu-20.04 or ubuntu-22.04. For more information, see this GitHub blog post.