From 546f9374c396e0bfb58a1bc4801b39956d32a042 Mon Sep 17 00:00:00 2001 From: Anil Seervi <61609033+AnilSeervi@users.noreply.github.com> Date: Sun, 2 Oct 2022 14:08:18 +0530 Subject: [PATCH 1/8] Change keys nomenclature according to guidelines --- content/get-started/using-github/keyboard-shortcuts.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/get-started/using-github/keyboard-shortcuts.md b/content/get-started/using-github/keyboard-shortcuts.md index bbd743e04a..ef9fa51a21 100644 --- a/content/get-started/using-github/keyboard-shortcuts.md +++ b/content/get-started/using-github/keyboard-shortcuts.md @@ -150,7 +150,7 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | Keyboard shortcut | Description |-----------|------------ -|⌘+f (Mac) or Ctrl+f (Windows/Linux) | Focus filter field +|Command+f (Mac) or Ctrl+f (Windows/Linux) | Focus filter field |← | Move cell focus to the left |→ | Move cell focus to the right |↑ | Move cell focus up @@ -162,7 +162,7 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |-----------|------------ |Enter | Toggle edit mode for the focused cell |Escape | Cancel editing for the focused cell -|⌘+Shift+\ (Mac) or Ctrl+Shift+\ (Windows/Linux) | Open row actions menu +|Command+Shift+\ (Mac) or Ctrl+Shift+\ (Windows/Linux) | Open row actions menu |Shift+Space | Select item |Space | Open selected item |e | Archive selected items From efb1b0c89de81942e7745d8d793cf689c2827c7c Mon Sep 17 00:00:00 2001 From: nrousset-socgen <58752118+nrousset-socgen@users.noreply.github.com> Date: Tue, 11 Oct 2022 16:51:20 +0200 Subject: [PATCH 2/8] Fix typo in URL --- .../duplicating-a-repository.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md b/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md index ea41e01734..ea7aab41cd 100644 --- a/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md +++ b/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md @@ -31,7 +31,7 @@ Before you can push the original repository to your new copy, or _mirror_, of th {% data reusables.command_line.open_the_multi_os_terminal %} 2. Create a bare clone of the repository. ```shell - $ git clone --bare https://{% data variables.command_line.codeblock %}/OLD-REPOSITORY.git/OLD-REPOSITORY.git + $ git clone --bare https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/OLD-REPOSITORY.git ``` 3. Mirror-push to the new repository. ```shell @@ -49,7 +49,7 @@ Before you can push the original repository to your new copy, or _mirror_, of th {% data reusables.command_line.open_the_multi_os_terminal %} 2. Create a bare clone of the repository. Replace the example username with the name of the person or organization who owns the repository, and replace the example repository name with the name of the repository you'd like to duplicate. ```shell - $ git clone --bare https://{% data variables.command_line.codeblock %}/OLD-REPOSITORY.git/OLD-REPOSITORY.git + $ git clone --bare https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/OLD-REPOSITORY.git ``` 3. Navigate to the repository you just cloned. ```shell @@ -61,7 +61,7 @@ Before you can push the original repository to your new copy, or _mirror_, of th ``` 5. Mirror-push to the new repository. ```shell - $ git push --mirror https://{% data variables.command_line.codeblock %}/OLD-REPOSITORY.git/NEW-REPOSITORY.git + $ git push --mirror https://{% data variables.command_line.codeblock %}EXAMPLE-USER/NEW-REPOSITORY.git ``` 6. Push the repository's {% data variables.large_files.product_name_long %} objects to your mirror. ```shell From 6c51c13392b2edb3bc5954a7e30feca4aa9ab3be Mon Sep 17 00:00:00 2001 From: Sarah Schneider Date: Wed, 12 Oct 2022 08:58:46 -0400 Subject: [PATCH 3/8] Support deep links on homepage (#31172) Co-authored-by: Peter Bengtsson --- content/index.md | 4 ++++ lib/all-products.js | 35 +++++++++++++++++++++++++++-------- middleware/context.js | 4 ++-- tests/rendering/server.js | 22 +++++++++++++--------- 4 files changed, 46 insertions(+), 19 deletions(-) diff --git a/content/index.md b/content/index.md index 483ef9a756..07ba324c2a 100644 --- a/content/index.md +++ b/content/index.md @@ -75,6 +75,10 @@ childGroups: octicon: ShieldLockIcon children: - code-security + - code-security/supply-chain-security + - code-security/dependabot + - code-security/code-scanning + - code-security/secret-scanning - name: Client apps octicon: DeviceMobileIcon children: diff --git a/lib/all-products.js b/lib/all-products.js index 7364b34cba..0d941c3afa 100644 --- a/lib/all-products.js +++ b/lib/all-products.js @@ -9,7 +9,6 @@ const homepage = path.posix.join(process.cwd(), 'content/index.md') const { data } = frontmatter(await fs.readFile(homepage, 'utf8')) export const productIds = data.children -export const productGroups = [] const externalProducts = data.externalProducts const internalProducts = {} @@ -45,17 +44,37 @@ for (const productId of productIds) { export const productMap = Object.assign({}, internalProducts, externalProducts) -for (const group of data.childGroups) { - productGroups.push({ - name: group.name, - icon: group.icon || null, - octicon: group.octicon || null, - children: group.children.map((id) => productMap[id]), +function getPage(id, lang, pageMap) { + const productId = id.split('/')[0] + const product = productMap[productId] + const href = removeFPTFromPath(path.posix.join('/', lang, product.versions[0], id)) + const page = pageMap[href] + if (!page) { + throw new Error(`Unable to find a page by the href '${href}'. Review your 'childGroups' frontmatter maybe.`) + } + // Return only the props needed for the ProductSelectionCard, since + // that's the only place this is ever used. + return { + id, + name: page.shortTitle || page.title, + href: href.replace(`/${lang}/`, '/'), + versions: page.applicableVersions, + } +} + +export function getProductGroups(pageMap, lang) { + return data.childGroups.map((group) => { + return { + name: group.name, + icon: group.icon || null, + octicon: group.octicon || null, + // Typically the children are product IDs, but we support deeper page paths too + children: group.children.map((id) => productMap[id] || getPage(id, lang, pageMap)), + } }) } export default { productIds, productMap, - productGroups, } diff --git a/middleware/context.js b/middleware/context.js index c935660f2b..6cc53abb73 100644 --- a/middleware/context.js +++ b/middleware/context.js @@ -1,7 +1,7 @@ import languages from '../lib/languages.js' import enterpriseServerReleases from '../lib/enterprise-server-releases.js' import { allVersions } from '../lib/all-versions.js' -import { productMap, productGroups } from '../lib/all-products.js' +import { productMap, getProductGroups } from '../lib/all-products.js' import pathUtils from '../lib/path-utils.js' import productNames from '../lib/product-names.js' import warmServer from '../lib/warm-server.js' @@ -39,7 +39,7 @@ export default async function contextualize(req, res, next) { req.context.currentProduct = getProductStringFromPath(req.pagePath) req.context.currentCategory = getCategoryStringFromPath(req.pagePath) req.context.productMap = productMap - req.context.productGroups = productGroups + req.context.productGroups = getProductGroups(pageMap, req.language) req.context.activeProducts = activeProducts req.context.allVersions = allVersions req.context.currentPathWithoutLanguage = getPathWithoutLanguage(req.pagePath) diff --git a/tests/rendering/server.js b/tests/rendering/server.js index 66f71f47d5..0f09e56839 100644 --- a/tests/rendering/server.js +++ b/tests/rendering/server.js @@ -6,6 +6,7 @@ import { loadPages } from '../../lib/page-data.js' import CspParse from 'csp-parse' import { productMap } from '../../lib/all-products.js' import { SURROGATE_ENUMS } from '../../middleware/set-fastly-surrogate-key.js' +import { getPathWithoutVersion } from '../../lib/path-utils.js' import { describe, jest } from '@jest/globals' const AZURE_STORAGE_URL = 'githubdocs.azureedge.net' @@ -79,21 +80,24 @@ describe('server', () => { test('renders the Enterprise homepages with links to expected products in both the sidebar and page body', async () => { const enterpriseProducts = [ - `/en/enterprise-server@${enterpriseServerReleases.latest}`, - '/en/enterprise-cloud@latest', + `enterprise-server@${enterpriseServerReleases.latest}`, + 'enterprise-cloud@latest', ] - enterpriseProducts.forEach(async (ep) => { - const $ = await getDOM(ep) + for (const ep of enterpriseProducts) { + const $ = await getDOM(`/en/${ep}`) const sidebarItems = $('[data-testid=sidebar] li a').get() const sidebarTitles = sidebarItems.map((el) => $(el).text().trim()) const sidebarHrefs = sidebarItems.map((el) => $(el).attr('href')) - const productItems = $('[data-testid=product] div a').get() - const productTitles = productItems.map((el) => $(el).text().trim()) - const productHrefs = productItems.map((el) => $(el).attr('href')) + const productItems = activeProducts.filter( + (prod) => prod.external || prod.versions.includes(ep) + ) + const productTitles = productItems.map((prod) => prod.name) + const productHrefs = productItems.map((prod) => + prod.external ? prod.href : `/en/${ep}${getPathWithoutVersion(prod.href)}` + ) const titlesInProductsButNotSidebar = lodash.difference(productTitles, sidebarTitles) - const hrefsInProductsButNotSidebar = lodash.difference(productHrefs, sidebarHrefs) expect( @@ -104,7 +108,7 @@ describe('server', () => { hrefsInProductsButNotSidebar.length, `Found hrefs missing from sidebar: ${hrefsInProductsButNotSidebar.join(', ')}` ).toBe(0) - }) + } }) test('sets Content Security Policy (CSP) headers', async () => { From 7b6a9694a8cb7f59ef5eb28968362f71be98aaa1 Mon Sep 17 00:00:00 2001 From: Stu Eggerton Date: Thu, 13 Oct 2022 02:43:03 +1100 Subject: [PATCH 4/8] fix regression in AE documentation (#31596) --- .../transferring-a-repository.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/content/repositories/creating-and-managing-repositories/transferring-a-repository.md index 92900222ad..dff4c98d4d 100644 --- a/content/repositories/creating-and-managing-repositories/transferring-a-repository.md +++ b/content/repositories/creating-and-managing-repositories/transferring-a-repository.md @@ -30,7 +30,7 @@ Prerequisites for repository transfers: - When you transfer a repository that you own to another personal account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %} - To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization. - The target account must not have a repository with the same name, or a fork in the same network. -- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghes < 3.7 %} +- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghes < 3.7 or ghae %} - Internal repositories can't be transferred.{% endif %} - Private forks can't be transferred. From 72d40de41459fd23091ab20deadd2b53cbea1f11 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Wed, 12 Oct 2022 18:43:58 +0200 Subject: [PATCH 5/8] make getMainContext async (#31622) --- components/context/MainContext.tsx | 2 +- components/playground/PlaygroundArticlePage.tsx | 2 +- pages/[versionId]/[productId]/index.tsx | 2 +- pages/[versionId]/admin/release-notes.tsx | 2 +- pages/[versionId]/graphql/overview/breaking-changes.tsx | 2 +- pages/[versionId]/graphql/overview/changelog.tsx | 2 +- pages/[versionId]/graphql/overview/explorer.tsx | 2 +- pages/[versionId]/graphql/overview/schema-previews.tsx | 2 +- pages/[versionId]/graphql/reference/[page].tsx | 2 +- pages/[versionId]/rest/[category]/[subcategory].tsx | 2 +- pages/[versionId]/rest/[category]/index.tsx | 2 +- .../rest/overview/endpoints-available-for-github-apps.tsx | 2 +- pages/index.tsx | 2 +- pages/search.tsx | 2 +- 14 files changed, 14 insertions(+), 14 deletions(-) diff --git a/components/context/MainContext.tsx b/components/context/MainContext.tsx index b4e6d511ce..e06ef3cfcf 100644 --- a/components/context/MainContext.tsx +++ b/components/context/MainContext.tsx @@ -125,7 +125,7 @@ export type MainContextT = { fullUrl: string } -export const getMainContext = (req: any, res: any): MainContextT => { +export const getMainContext = async (req: any, res: any): Promise => { // Our current translation process adds 'ms.*' frontmatter properties to files // it translates including when data/ui.yml is translated. We don't use these // properties and their syntax (e.g. 'ms.openlocfilehash', diff --git a/components/playground/PlaygroundArticlePage.tsx b/components/playground/PlaygroundArticlePage.tsx index 07d4638410..d2ce7a7d12 100644 --- a/components/playground/PlaygroundArticlePage.tsx +++ b/components/playground/PlaygroundArticlePage.tsx @@ -88,7 +88,7 @@ export const getServerSideProps: GetServerSideProps = async (context) => return { props: { - mainContext: getMainContext(req, res), + mainContext: await getMainContext(req, res), }, } } diff --git a/pages/[versionId]/[productId]/index.tsx b/pages/[versionId]/[productId]/index.tsx index dd0393ac35..63fba249ca 100644 --- a/pages/[versionId]/[productId]/index.tsx +++ b/pages/[versionId]/[productId]/index.tsx @@ -107,7 +107,7 @@ export const getServerSideProps: GetServerSideProps = async (context) => const res = context.res as any const props: Props = { - mainContext: getMainContext(req, res), + mainContext: await getMainContext(req, res), } const { currentLayoutName, relativePath } = props.mainContext diff --git a/pages/[versionId]/admin/release-notes.tsx b/pages/[versionId]/admin/release-notes.tsx index 5d51e042ab..3f12f960df 100644 --- a/pages/[versionId]/admin/release-notes.tsx +++ b/pages/[versionId]/admin/release-notes.tsx @@ -31,7 +31,7 @@ export const getServerSideProps: GetServerSideProps = async (context) => const { latestPatch = '', latestRelease = '' } = req.context return { props: { - mainContext: getMainContext(req, res), + mainContext: await getMainContext(req, res), ghesContext: currentVersion.plan === 'enterprise-server' ? { diff --git a/pages/[versionId]/graphql/overview/breaking-changes.tsx b/pages/[versionId]/graphql/overview/breaking-changes.tsx index b2a6ab79b2..5f1d28f723 100644 --- a/pages/[versionId]/graphql/overview/breaking-changes.tsx +++ b/pages/[versionId]/graphql/overview/breaking-changes.tsx @@ -53,7 +53,7 @@ export const getServerSideProps: GetServerSideProps = async (context) => return { props: { - mainContext: getMainContext(req, res), + mainContext: await getMainContext(req, res), automatedPageContext, schema, }, diff --git a/pages/[versionId]/graphql/overview/changelog.tsx b/pages/[versionId]/graphql/overview/changelog.tsx index 22dd4ff710..b8b21d6d47 100644 --- a/pages/[versionId]/graphql/overview/changelog.tsx +++ b/pages/[versionId]/graphql/overview/changelog.tsx @@ -46,7 +46,7 @@ export const getServerSideProps: GetServerSideProps = async (context) => return { props: { - mainContext: getMainContext(req, res), + mainContext: await getMainContext(req, res), automatedPageContext, schema, }, diff --git a/pages/[versionId]/graphql/overview/explorer.tsx b/pages/[versionId]/graphql/overview/explorer.tsx index 4b5899ffd3..7bc7456d77 100644 --- a/pages/[versionId]/graphql/overview/explorer.tsx +++ b/pages/[versionId]/graphql/overview/explorer.tsx @@ -52,7 +52,7 @@ export const getServerSideProps: GetServerSideProps = async (context) => return { props: { - mainContext: getMainContext(req, res), + mainContext: await getMainContext(req, res), graphqlExplorerUrl, }, } diff --git a/pages/[versionId]/graphql/overview/schema-previews.tsx b/pages/[versionId]/graphql/overview/schema-previews.tsx index 1e518d5f87..5eafe01b23 100644 --- a/pages/[versionId]/graphql/overview/schema-previews.tsx +++ b/pages/[versionId]/graphql/overview/schema-previews.tsx @@ -48,7 +48,7 @@ export const getServerSideProps: GetServerSideProps = async (context) => return { props: { - mainContext: getMainContext(req, res), + mainContext: await getMainContext(req, res), automatedPageContext, schema, }, diff --git a/pages/[versionId]/graphql/reference/[page].tsx b/pages/[versionId]/graphql/reference/[page].tsx index ab33d5089b..23c5cc0807 100644 --- a/pages/[versionId]/graphql/reference/[page].tsx +++ b/pages/[versionId]/graphql/reference/[page].tsx @@ -66,7 +66,7 @@ export const getServerSideProps: GetServerSideProps = async (context) => return { props: { - mainContext: getMainContext(req, res), + mainContext: await getMainContext(req, res), automatedPageContext, schema, language, diff --git a/pages/[versionId]/rest/[category]/[subcategory].tsx b/pages/[versionId]/rest/[category]/[subcategory].tsx index 8ea6cb1458..d92f7cfdf9 100644 --- a/pages/[versionId]/rest/[category]/[subcategory].tsx +++ b/pages/[versionId]/rest/[category]/[subcategory].tsx @@ -74,7 +74,7 @@ export const getServerSideProps: GetServerSideProps = async (context) => return { props: { restOperations, - mainContext: getMainContext(req, res), + mainContext: await getMainContext(req, res), automatedPageContext: getAutomatedPageContextFromRequest(req), }, } diff --git a/pages/[versionId]/rest/[category]/index.tsx b/pages/[versionId]/rest/[category]/index.tsx index aa92bb9802..f266278930 100644 --- a/pages/[versionId]/rest/[category]/index.tsx +++ b/pages/[versionId]/rest/[category]/index.tsx @@ -193,7 +193,7 @@ export const getServerSideProps: GetServerSideProps = async (context) => return { props: { restOperations, - mainContext: getMainContext(req, res), + mainContext: await getMainContext(req, res), automatedPageContext: getAutomatedPageContextFromRequest(req), tocLandingContext, }, diff --git a/pages/[versionId]/rest/overview/endpoints-available-for-github-apps.tsx b/pages/[versionId]/rest/overview/endpoints-available-for-github-apps.tsx index acd9fc87ce..dea06fe6eb 100644 --- a/pages/[versionId]/rest/overview/endpoints-available-for-github-apps.tsx +++ b/pages/[versionId]/rest/overview/endpoints-available-for-github-apps.tsx @@ -92,7 +92,7 @@ export const getServerSideProps: GetServerSideProps = async (context) => const req = context.req as object const res = context.res as object const currentVersion = context.query.versionId as string - const mainContext = getMainContext(req, res) + const mainContext = await getMainContext(req, res) const automatedPageContext = getAutomatedPageContextFromRequest(req) if (!enabledForApps) { diff --git a/pages/index.tsx b/pages/index.tsx index e3b00cc927..751d5d1997 100644 --- a/pages/index.tsx +++ b/pages/index.tsx @@ -66,7 +66,7 @@ export const getServerSideProps: GetServerSideProps = async (context) => return { props: { - mainContext: getMainContext(req, res), + mainContext: await getMainContext(req, res), gettingStartedLinks: req.context.featuredLinks.gettingStarted.map( ({ title, href, intro }: any) => ({ title, href, intro }) ), diff --git a/pages/search.tsx b/pages/search.tsx index 8b29825278..830f7a3999 100644 --- a/pages/search.tsx +++ b/pages/search.tsx @@ -42,7 +42,7 @@ export const getServerSideProps: GetServerSideProps = async (context) => } } - const mainContext = getMainContext(req, res) + const mainContext = await getMainContext(req, res) return { props: { From b1dc21ccbdc58ad6fcee9a66e5b8355caa4a3f70 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Wed, 12 Oct 2022 19:04:23 +0200 Subject: [PATCH 6/8] make 'All products' link a Router link (#31642) --- components/sidebar/AllProductsLink.tsx | 5 +++-- lib/all-products.js | 6 ++++-- 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/components/sidebar/AllProductsLink.tsx b/components/sidebar/AllProductsLink.tsx index beecbab575..db98f99a13 100644 --- a/components/sidebar/AllProductsLink.tsx +++ b/components/sidebar/AllProductsLink.tsx @@ -1,6 +1,7 @@ import { useRouter } from 'next/router' import { ArrowLeftIcon } from '@primer/octicons-react' import { DEFAULT_VERSION, useVersion } from 'components/hooks/useVersion' +import { Link } from 'components/Link' export const AllProductsLink = () => { const router = useRouter() @@ -9,13 +10,13 @@ export const AllProductsLink = () => { return (
  • - All products - +
    • ) } diff --git a/lib/all-products.js b/lib/all-products.js index 0d941c3afa..1593436582 100644 --- a/lib/all-products.js +++ b/lib/all-products.js @@ -49,8 +49,10 @@ function getPage(id, lang, pageMap) { const product = productMap[productId] const href = removeFPTFromPath(path.posix.join('/', lang, product.versions[0], id)) const page = pageMap[href] - if (!page) { - throw new Error(`Unable to find a page by the href '${href}'. Review your 'childGroups' frontmatter maybe.`) + if (!page) { + throw new Error( + `Unable to find a page by the href '${href}'. Review your 'childGroups' frontmatter maybe.` + ) } // Return only the props needed for the ProductSelectionCard, since // that's the only place this is ever used. From 32127b779d156af46fdf823dc0356788da4e1aec Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Wed, 12 Oct 2022 10:41:35 -0700 Subject: [PATCH 7/8] New translation batch for ja (#31648) --- .../personalizing-your-profile.md | 196 ++++++++++-------- .../security-hardening-for-github-actions.md | 2 +- ...rise-server-with-github-actions-enabled.md | 65 +++--- .../setting-up-a-staging-instance.md | 158 +++++++++++--- .../using-github/keyboard-shortcuts.md | 4 +- translations/ja-JP/content/index.md | 4 + ...analysis-settings-for-your-organization.md | 171 +++++++++------ .../transferring-a-repository.md | 2 +- translations/log/msft-ja-resets.csv | 8 +- 9 files changed, 388 insertions(+), 222 deletions(-) diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md index 179729b210..850fdd4282 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md @@ -1,6 +1,6 @@ --- -title: プロフィールをパーソナライズする -intro: 'プロフィール画像を設定し、プロフィールに略歴を追加することで、自分自身についての情報を他の {% data variables.product.product_name %} ユーザと共有することができます。' +title: Personalizing your profile +intro: 'You can share information about yourself with other {% data variables.product.product_name %} users by setting a profile picture and adding a bio to your profile.' redirect_from: - /articles/adding-a-bio-to-your-profile - /articles/setting-your-profile-picture @@ -18,156 +18,186 @@ versions: topics: - Profiles shortTitle: Personalize -ms.openlocfilehash: c12fccd91144428fe9aad2f01d2c0b0941fdd4d4 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146681054' --- -## プロフィール画像を変更する +## Changing your profile picture -プロフィール画像は、{% data variables.product.product_name %} のプルリクエスト、コメント、コントリビューションページ、およびグラフにおいて、あなたを識別するのに役立ちます。 +Your profile picture helps identify you across {% data variables.product.product_name %} in pull requests, comments, contributions pages, and graphs. -アカウントにサインアップすると、{% data variables.product.product_name %} はとりあえずランダムなアイデンティコンを生成します。 [アイデンティコン](https://github.com/blog/1586-identicons)はユーザー ID のハッシュから生成されるので、その色やパターンを制御する方法はありません。 アイデンティコンは、あなたを表す画像に置き換えることができます。 +When you sign up for an account, {% data variables.product.product_name %} provides you with a randomly generated "identicon". [Your identicon](https://github.com/blog/1586-identicons) generates from a hash of your user ID, so there's no way to control its color or pattern. You can replace your identicon with an image that represents you. {% note %} -**注{% ifversion ghec %}{% endif %}** : {% ifversion ghec %} +**Note{% ifversion ghec %}s{% endif %}**: {% ifversion ghec %} -* {% endif %}プロフィール画像は、PNG、JPG、または GIF ファイルでなければならず、1 MB 未満のサイズで、3000 x 3000 ピクセルより小さいものにする必要があります。 最高の画質をもたらすには、画像を 500 × 500 ピクセルに収めることを推奨します。 -{% ifversion ghec %}* Gravatar プロファイル画像は {% data variables.product.prodname_emus %} ではサポートされていません。{% endif %} +* {% endif %}Your profile picture should be a PNG, JPG, or GIF file, and it must be less than 1 MB in size and smaller than 3000 by 3000 pixels. For the best quality rendering, we recommend keeping the image at about 500 by 500 pixels. +{% ifversion ghec %}* Gravatar profile pictures are not supported with {% data variables.product.prodname_emus %}.{% endif %} {% endnote %} -### プロフィール画像を設定する +### Setting a profile picture {% data reusables.user-settings.access_settings %} -2. **[Profile Picture]\(プロファイル画像\)** の下にある {% octicon "pencil" aria-label="The edit icon" %} **[Edit]\(編集\)** をクリックします。 -![プロファイル画像を編集する](/assets/images/help/profile/edit-profile-photo.png) -3. **[写真のアップロード]** をクリックします。{% ifversion not ghae %} ![プロフィール画像を更新する](/assets/images/help/profile/edit-profile-picture-options.png){% endif %} -3. 画像をクロッピングします。 作業を終えたら **[Set new profile picture]\(新しいプロファイル画像の設定\)** をクリックします。 - ![アップロードした画像をトリミングする](/assets/images/help/profile/avatar_crop_and_save.png) +2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**. +![Edit profile picture](/assets/images/help/profile/edit-profile-photo.png) +3. Click **Upload a photo...**.{% ifversion not ghae %} +![Update profile picture](/assets/images/help/profile/edit-profile-picture-options.png){% endif %} +3. Crop your picture. When you're done, click **Set new profile picture**. + ![Crop uploaded photo](/assets/images/help/profile/avatar_crop_and_save.png) -### プロフィール画像をアイデンティコンへリセットする +### Resetting your profile picture to the identicon {% data reusables.user-settings.access_settings %} -2. **[Profile Picture]\(プロファイル画像\)** の下にある {% octicon "pencil" aria-label="The edit icon" %} **[Edit]\(編集\)** をクリックします。 -![プロファイル画像を編集する](/assets/images/help/profile/edit-profile-photo.png) -3. アイデンティコンに戻すには、 **[Remove photo]\(画像の削除\)** をクリックします。 {% ifversion not ghae %}メール アドレスが [Gravatar](https://en.gravatar.com/) に関連付けられている場合、アイデンティコンに戻すことはできません。 代わりに **[Revert to Gravatar]\(Gravatar に戻す\)** をクリックします。 -![プロフィール画像を更新する](/assets/images/help/profile/edit-profile-picture-options.png){% endif %} +2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**. +![Edit profile picture](/assets/images/help/profile/edit-profile-photo.png) +3. To revert to your identicon, click **Remove photo**. {% ifversion not ghae %}If your email address is associated with a [Gravatar](https://en.gravatar.com/), you cannot revert to your identicon. Click **Revert to Gravatar** instead. +![Update profile picture](/assets/images/help/profile/edit-profile-picture-options.png){% endif %} -## プロフィール名を変更する +## Changing your profile name -プロフィールに表示される名前は変更可能です。 この名前は、Organization が所有するプライベートリポジトリへのコメントの横に表示されることもあります。 詳細については、「[組織のメンバー名表示を管理する](/articles/managing-the-display-of-member-names-in-your-organization)」を参照してください。 +You can change the name that is displayed on your profile. This name may also be displayed next to comments you make on private repositories owned by an organization. For more information, see "[Managing the display of member names in your organization](/articles/managing-the-display-of-member-names-in-your-organization)." -{% ifversion fpt or ghec %} {% note %} +{% ifversion fpt or ghec %} +{% note %} -**注:** {% data variables.product.prodname_emu_enterprise %} のメンバーである場合、プロファイル名の変更は {% data variables.product.prodname_dotcom_the_website %} ではなく、ID プロバイダーを介して行う必要があります。 {% data reusables.enterprise-accounts.emu-more-info-account %} +**Note:** If you're a member of an {% data variables.product.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} -{% endnote %} {% endif %} +{% endnote %} +{% endif %} {% data reusables.user-settings.access_settings %} -2. [Name] の下に、プロフィールに表示する名前を入力します。 - ![プロファイル設定の [Name]\(名前\) フィールド](/assets/images/help/profile/name-field.png) +2. Under "Name", type the name you want to be displayed on your profile. + ![Name field in profile settings](/assets/images/help/profile/name-field.png) -## プロフィールに略歴を追加する +## Adding a bio to your profile -自分に関する情報を他の {% data variables.product.product_name %} ユーザーと共有するには、プロフィールに略歴を追加します。 [@mentions](/articles/basic-writing-and-formatting-syntax) と絵文字を使えば、あなたの現在または過去の職場、職種、飲んでいるコーヒーの種類といった情報も含めることができます。 +Add a bio to your profile to share information about yourself with other {% data variables.product.product_name %} users. With the help of [@mentions](/articles/basic-writing-and-formatting-syntax) and emoji, you can include information about where you currently or have previously worked, what type of work you do, or even what kind of coffee you drink. {% ifversion fpt or ghes or ghec %} -自分に関するカスタマイズした情報を長いフォームで、もっと目立つように表示する場合は、プロフィール README を使用することもできます。 詳細については、「[プロファイルの README を管理する](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)」を参照してください。 +For a longer-form and more prominent way of displaying customized information about yourself, you can also use a profile README. For more information, see "[Managing your profile README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)." {% endif %} {% note %} -**注:** プロファイルでアクティビティ概要のセクションを有効にしており、プロファイルの略歴で自分がメンバーである組織に @mention した場合、アクティビティの概要ではその組織が最初に表示されます。 詳細については、「[プロファイルでアクティビティの概要を表示する](/articles/showing-an-overview-of-your-activity-on-your-profile)」を参照してください。 +**Note:** + If you have the activity overview section enabled for your profile and you @mention an organization you're a member of in your profile bio, then that organization will be featured first in your activity overview. For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)." {% endnote %} {% data reusables.user-settings.access_settings %} -2. **[Bio]\(略歴\)** の下で、自分のプロファイルに表示する内容を追加します。 略歴フィールドの上限は 160 文字です。 - ![プロファイルの略歴を更新する](/assets/images/help/profile/bio-field.png) +2. Under **Bio**, add the content that you want displayed on your profile. The bio field is limited to 160 characters. + ![Update bio on profile](/assets/images/help/profile/bio-field.png) {% tip %} - **ヒント:** 組織に @mention すると、自分がメンバーであるものだけがオートコンプリートされます。 以前の職場など、自分がメンバーではない組織に @mention することもできますが、その組織の名前はオートコンプリートされません。 + **Tip:** When you @mention an organization, only those that you're a member of will autocomplete. You can still @mention organizations that you're not a member of, like a previous employer, but the organization name won't autocomplete for you. {% endtip %} -3. **[プロファイルの更新]** をクリックします。 - ![[Update profile]\(プロファイルの更新\) ボタン](/assets/images/help/profile/update-profile-button.png) +{% data reusables.profile.update-profile %} -## ステータスを設定する +{% ifversion profile-time-zone %} -ステータスを設定すると、あなたの現在の状況に関する情報を {% data variables.product.product_name %} に表示することができます。 ステータスは次の場所や状況で表示されます: -- {% data variables.product.product_name %} のプロフィールページ。 -- {% data variables.product.product_name %} でユーザがあなたのユーザ名やアバターにカーソルを置いたとき。 -- 自分が Team メンバーになっている Team の Team ページ。 詳細については、「[Team について](/articles/about-teams/#team-pages)」を参照してください。 -- メンバーになっている Organization の Organization ダッシュボード。 詳細については、「[Organization ダッシュボードについて](/articles/about-your-organization-dashboard/)」を参照してください。 +## Setting your location and time zone -ステータスを設定すると、あなたの時間的な制約について、{% data variables.product.product_name %} で他のユーザーに知らせることもできます。 +You can set a location and time zone on your profile to show other people your local time. Your location and time zone will be visible: +- on your {% data variables.product.product_name %} profile page. +- when people hover over your username or avatar on {% data variables.product.product_name %}. -![@メンションされたユーザー名の横に "busy"(ビジー) ノートが表示される](/assets/images/help/profile/username-with-limited-availability-text.png) +When you view your profile, you will see your location, local time, and your time zone in relation to Universal Time Coordinated. -![依頼されたレビュー担当者には、ユーザー名の横に "busy"(ビジー) ノートが表示されます。](/assets/images/help/profile/request-a-review-limited-availability-status.png) + ![Screenshot of the Octocat profile page emphasizing the location, local time, and time zone fields.](/assets/images/help/profile/profile-location-and-time.png) -[Busy]\(ビジー\) オプションを選ぶと、自分のユーザー名に誰かが @mention したとき、自分に issue や pull request が割り当てられたとき、または自分が pull request レビューをリクエストしたとき、ユーザー名の横にビジーであることを示すノートが表示されます。 また、自分が所属するチームに割り当てられた pull request の自動レビュー割り当てからも除外されます。 詳細については、「[チームのコード レビュー設定の管理](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)」を参照してください。 +When others view your profile, they will see your location, local time, and the time difference in hours from their own local time. -1. {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %} の右上にあるプロファイル画像をクリックし、 **[Set your status]\(ステータスの設定\)** をクリックします。または既にステータスが設定されている場合は、現在のステータスをクリックします。 - ![ステータスを設定するプロファイルのボタン](/assets/images/help/profile/set-status-on-profile.png) -2. ステータスにカスタムテキストを追加する場合は、テキストフィールドをクリックしてステータスメッセージを入力します。 - ![ステータス メッセージを入力するフィールド](/assets/images/help/profile/type-a-status-message.png) -3. オプションで、ステータス絵文字を設定する場合は、絵文字のアイコンをクリックしてリストから選択します。 - ![絵文字のステータスを選ぶボタン](/assets/images/help/profile/select-emoji-status.png) -4. オプションで、時間に制約があるという情報を共有するには、[Busy] を選択します。 - ![[Edit status]\(ステータスの編集\) オプションで選ばれている [Busy]\(ビジー\) オプション](/assets/images/help/profile/limited-availability-status.png) -5. **[Clear status]\(ステータスのクリア\)** ドロップダウン メニューを使って、ステータスの有効期限を選びます。 ステータスの有効期限を設定しない場合は、クリアするか編集するまで同じステータスのままになります。 - ![ステータスの有効期限が切れたときに選ぶドロップダウン メニュー](/assets/images/help/profile/status-expiration.png) -6. ドロップダウンメニューを使って、ステータスを表示する Organization をクリックします。 Organization を選択しない場合、あなたのステータスはパブリックになります。 - ![ステータスが表示されるときに選ぶドロップダウン メニュー](/assets/images/help/profile/status-visibility.png) -7. **[Set status]\(ステータスの設定\)** をクリックします。 - ![ステータスを設定するボタン](/assets/images/help/profile/set-status-button.png) + ![Screenshot of the Octocat profile page emphasizing the location, local time, and relative time fields.](/assets/images/help/profile/profile-relative-time.png) + +{% data reusables.user-settings.access_settings %} +1. Under **Location**, type the location you want to be displayed on your profile. + + ![Screenshot of the location and local time settings emphasizing the location field.](/assets/images/help/profile/location-field.png) + +1. Optionally, to display the current local time on your profile, select **Display current local time**. + + ![Screenshot of the location and local time settings emphasizing the display current local time checkbox.](/assets/images/help/profile/display-local-time-checkbox.png) + + - Select the **Time zone** dropdown menu, then click your local time zone. + + ![Screenshot of the location and local time settings emphasizing the time zone dropdown menu.](/assets/images/help/profile/time-zone-dropdown.png) + +{% data reusables.profile.update-profile %} + +{% endif %} + +## Setting a status + +You can set a status to display information about your current availability on {% data variables.product.product_name %}. Your status will show: +- on your {% data variables.product.product_name %} profile page. +- when people hover over your username or avatar on {% data variables.product.product_name %}. +- on a team page for a team where you're a team member. For more information, see "[About teams](/articles/about-teams/#team-pages)." +- on the organization dashboard in an organization where you're a member. For more information, see "[About your organization dashboard](/articles/about-your-organization-dashboard/)." + +When you set your status, you can also let people know that you have limited availability on {% data variables.product.product_name %}. + +![At-mentioned username shows "busy" note next to username](/assets/images/help/profile/username-with-limited-availability-text.png) + +![Requested reviewer shows "busy" note next to username](/assets/images/help/profile/request-a-review-limited-availability-status.png) + +If you select the "Busy" option, when people @mention your username, assign you an issue or pull request, or request a pull request review from you, a note next to your username will show that you're busy. You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." + +1. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Set your status** or, if you already have a status set, click your current status. + ![Button on profile to set your status](/assets/images/help/profile/set-status-on-profile.png) +2. To add custom text to your status, click in the text field and type a status message. + ![Field to type a status message](/assets/images/help/profile/type-a-status-message.png) +3. Optionally, to set an emoji status, click the smiley icon and select an emoji from the list. + ![Button to select an emoji status](/assets/images/help/profile/select-emoji-status.png) +4. Optionally, if you'd like to share that you have limited availability, select "Busy." + ![Busy option selected in Edit status options](/assets/images/help/profile/limited-availability-status.png) +5. Use the **Clear status** drop-down menu, and select when you want your status to expire. If you don't select a status expiration, you will keep your status until you clear or edit your status. + ![Drop down menu to choose when your status expires](/assets/images/help/profile/status-expiration.png) +6. Use the drop-down menu and click the organization you want your status visible to. If you don't select an organization, your status will be public. + ![Drop down menu to choose who your status is visible to](/assets/images/help/profile/status-visibility.png) +7. Click **Set status**. + ![Button to set status](/assets/images/help/profile/set-status-button.png) {% ifversion fpt or ghec %} -## プロフィールでバッジを表示する +## Displaying badges on your profile -特定のプログラムに参加すると、{% data variables.product.prodname_dotcom %} でプロフィールに自動的にバッジが表示されます。 +When you participate in certain programs, {% data variables.product.prodname_dotcom %} automatically displays a badge on your profile. -| バッジ | プログラム | 説明 | +| Badge | Program | Description | | --- | --- | --- | -| {% octicon "cpu" aria-label="The Developer Program icon" %} | **開発者プログラム メンバー** | {% data variables.product.prodname_dotcom %} 開発者プログラムの登録メンバーである場合は、{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API を使ってアプリをビルドすると、プロファイルに開発者プログラム メンバー バッジが表示されます。 {% data variables.product.prodname_dotcom %} 開発者プログラムの詳細については、[GitHub 開発者](/program/)に関するページを参照してください。 | -| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | {% data variables.product.prodname_pro %} を使用すると、プロフィールで PRO バッジを取得します。 {% data variables.product.prodname_pro %} の詳細については、「[{% data variables.product.prodname_dotcom %} の製品](/github/getting-started-with-github/githubs-products#github-pro)」を参照してください。 | -| {% octicon "lock" aria-label="The lock icon" %} | **セキュリティ バグ バウンティ ハンター** | セキュリティの脆弱性検出を支援した場合、プロファイルにセキュリティ バグ バウンティ ハンター バッジが表示されます。 {% data variables.product.prodname_dotcom %} セキュリティ プログラムの詳細については、[{% data variables.product.prodname_dotcom %} のセキュリティ](https://bounty.github.com/)に関するページを参照してください。 | -| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **{% data variables.product.prodname_dotcom %} キャンパス エキスパート** | {% data variables.product.prodname_campus_program %} に参加すると、プロファイルに {% data variables.product.prodname_dotcom %} キャンパス エキスパート バッジが表示されます。 キャンパス エキスパート プログラムの詳細については、[キャンパス エキスパート](https://education.github.com/experts)に関するページを参照してください。 | -| {% octicon "shield" aria-label="The shield icon" %} | **セキュリティ アドバイザリ クレジット** | [{% data variables.product.prodname_dotcom %} Advisory Database](https://github.com/advisories) に送信したセキュリティ アドバイザリが受け入れられると、プロフィールにセキュリティ アドバイザリ クレジット バッジが表示されます。 {% data variables.product.prodname_dotcom %} セキュリティ アドバイザリについて詳しくは、[{% data variables.product.prodname_dotcom %} セキュリティ アドバイザリ](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)に関するページをご覧ください。 | -| {% octicon "check" aria-label="The check icon" %} | **回答済みディスカッション** | ディスカッションへの返信が回答としてマークされている場合は、プロフィールに回答済みディスカッション バッジが表示されます。 {% data variables.product.prodname_dotcom %} のディスカッションについて詳しくは、「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」をご覧ください。 | +| {% octicon "cpu" aria-label="The Developer Program icon" %} | **Developer Program Member** | If you're a registered member of the {% data variables.product.prodname_dotcom %} Developer Program, building an app with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, you'll get a Developer Program Member badge on your profile. For more information on the {% data variables.product.prodname_dotcom %} Developer Program, see [GitHub Developer](/program/). | +| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | If you use {% data variables.product.prodname_pro %} you'll get a PRO badge on your profile. For more information about {% data variables.product.prodname_pro %}, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products#github-pro)." | +| {% octicon "lock" aria-label="The lock icon" %} | **Security Bug Bounty Hunter** | If you helped out hunting down security vulnerabilities, you'll get a Security Bug Bounty Hunter badge on your profile. For more information about the {% data variables.product.prodname_dotcom %} Security program, see [{% data variables.product.prodname_dotcom %} Security](https://bounty.github.com/). | +| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **{% data variables.product.prodname_dotcom %} Campus Expert** | If you participate in the {% data variables.product.prodname_campus_program %}, you will get a {% data variables.product.prodname_dotcom %} Campus Expert badge on your profile. For more information about the Campus Experts program, see [Campus Experts](https://education.github.com/experts). | +| {% octicon "shield" aria-label="The shield icon" %} | **Security advisory credit** | If a security advisory you submit to the [{% data variables.product.prodname_dotcom %} Advisory Database](https://github.com/advisories) is accepted, you'll get a Security advisory credit badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Security Advisories, see [{% data variables.product.prodname_dotcom %} Security Advisories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories). | +| {% octicon "check" aria-label="The check icon" %} | **Discussion answered** | If your reply to a discussion is marked as the answer, you'll get a Discussion answered badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Discussions, see [About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions). | {% endif %} {% ifversion fpt or ghec %} -## アチーブメントの獲得 +## Earning Achievements -アチーブメントは、{% data variables.product.prodname_dotcom %} で発生する特定のイベントとアクションを示します。 それは、プロフィールのサイドバーの小さなバッジとして表示されます。 アチーブメントをクリックまたはポイントすると、アチーブメントがどのようにして獲得されたのかがわかる詳細と、簡単な説明および関連するイベントへのリンクが表示されます。 イベント リンクは、イベントが発生したリポジトリまたは Organization にアクセスできるユーザーに対してだけ表示されます。 アクセス権のないすべてのユーザーには、アクセスできないイベント リンクが表示されます。 +Achievements celebrate specific events and actions that happen on {% data variables.product.prodname_dotcom %}. They will appear as small badges listed in the sidebar of your profile. Clicking or hovering on an achievement will show a detailed view that hints at how the achievement was earned, with a short description and links to the contributing events. The event links will only be visible to users that have access to the repository or organization that the event took place in. Event links will appear inaccessible to all users without access. -非公開の貢献がアチーブメントにカウントされないようにするには、またはアチーブメントを完全にオフにするには、「[プロフィールに非公開の貢献とアチーブメントを表示する](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)」をご覧ください。 +To stop private contributions from counting toward your Achievements, or to turn off Achievements entirely, see "[Showing your private contributions and Achievements on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)." {% note %} -**注:** この機能は現在ベータ版であり、変更されることがあります。 +**Note:** This feature is currently in beta and subject to change. {% endnote %} {% endif %} -## Mars 2020 ヘリコプター共同作成者アチーブメントの対象リポジトリの一覧 +## List of qualifying repositories for Mars 2020 Helicopter Contributor achievement -次に示す 1 つ以上のリポジトリの一覧にあるタグについて、コミット履歴に存在するコミットを作成した場合、Mars 2020 ヘリコプター共同作成者アチーブメントがプロフィールに表示されます。 {% data variables.product.prodname_dotcom %} が適格な貢献と判断した時点であなたのアカウントに関連付けられていた、検証済みメール アドレスを使って作成したコミットである必要があります。これは、あなたの貢献と判断するために必要です。 そのコミットの元の作成者または[共同作成者の 1 人](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)である場合があります。 将来的に検証済みメール アドレスを変更しても、このバッジに影響はありません。 NASA の Jet Propulsion 研究所から受け取った情報に基づいて一覧を作成しました。 +If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor achievement on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. You can be the original author or [one of the co-authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) of the commit. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory. -| {% data variables.product.prodname_dotcom %} リポジトリ | バージョン | タグ | +| {% data variables.product.prodname_dotcom %} Repository | Version | Tag | |---|---|---| | [torvalds/linux](https://github.com/torvalds/linux) | 3.4 | [v3.4](https://github.com/torvalds/linux/releases/tag/v3.4) | | [python/cpython](https://github.com/python/cpython) | 3.9.2 | [v3.9.2](https://github.com/python/cpython/releases/tag/v3.9.2) | @@ -238,6 +268,6 @@ ms.locfileid: '146681054' | [locationtech/jts](https://github.com/locationtech/jts) | 1.15.0 | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0) | | [apache/logging-log4j2](https://github.com/apache/logging-log4j2) | 2.11 | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0) | -## 参考資料 +## Further reading -- "[プロフィールについて](/articles/about-your-profile)" +- "[About your profile](/articles/about-your-profile)" diff --git a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md index c39ef22235..9b7fb1a826 100644 --- a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md @@ -275,7 +275,7 @@ This list describes the recommended approaches for accessing repository data wit {% ifversion fpt or ghec %}**Self-hosted**{% elsif ghes or ghae %}Self-hosted{% endif %} runners for {% data variables.product.product_name %} do not have guarantees around running in ephemeral clean virtual machines, and can be persistently compromised by untrusted code in a workflow. -{% ifversion fpt or ghec %}As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal repositories, as anyone who can fork the repository and open a pull request (generally those with read access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the `GITHUB_TOKEN` which, depending on its settings, can grant write access to the repository. Although workflows can control access to environment secrets by using environments and required reviews, these workflows are not run in an isolated environment and are still susceptible to the same risks when run on a self-hosted runner. +{% ifversion fpt or ghec %}As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal repositories, as anyone who can fork the repository and open a pull request (generally those with read access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the `GITHUB_TOKEN` which, depending on its settings, can grant write access to the repository. Although workflows can control access to environment secrets by using environments and required reviews, these workflows are not run in an isolated environment and are still susceptible to the same risks when run on a self-hosted runner. When a self-hosted runner is defined at the organization or enterprise level, {% data variables.product.product_name %} can schedule workflows from multiple repositories onto the same runner. Consequently, a security compromise of these environments can result in a wide impact. To help reduce the scope of a compromise, you can create boundaries by organizing your self-hosted runners into separate groups. You can restrict what {% ifversion restrict-groups-to-workflows %}workflows, {% endif %}organizations and repositories can access runner groups. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)." diff --git a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md index 5be57987a6..bd71918b12 100644 --- a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md +++ b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md @@ -1,7 +1,7 @@ --- -title: GitHub Actions を有効化して GitHub Enterprise Server をバックアップおよび復元する +title: Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled shortTitle: Backing up and restoring -intro: '外部ストレージプロバイダの {% data variables.product.prodname_actions %} データは、通常の {% data variables.product.prodname_ghe_server %} バックアップに含まれていないため、個別にバックアップする必要があります。' +intro: 'To restore a backup of {% data variables.product.product_location %} when {% data variables.product.prodname_actions %} is enabled, you must configure {% data variables.product.prodname_actions %} before restoring the backup with {% data variables.product.prodname_enterprise_backup_utilities %}.' versions: ghes: '*' type: how_to @@ -12,50 +12,33 @@ topics: - Infrastructure redirect_from: - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled -ms.openlocfilehash: def12b4e9e93a75ee1aa58f8290ca1b6e7d13cd5 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145120462' --- -{% data reusables.actions.enterprise-storage-ha-backups %} -{% data variables.product.prodname_enterprise_backup_utilities %} を使用して {% data variables.product.product_location %} をバックアップする場合、外部ストレージプロバイダに保存されている {% data variables.product.prodname_actions %} データはバックアップに含まれないことにご注意ください。 +## About backups of {% data variables.product.product_name %} when using {% data variables.product.prodname_actions %} -以下は、{% data variables.product.product_location %} と {% data variables.product.prodname_actions %} を新しいアプライアンスに復元するために必要なステップの概要です。 +You can use {% data variables.product.prodname_enterprise_backup_utilities %} to back up and restore the data and configuration for {% data variables.product.product_location %} to a new instance. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)." -1. 元のアプライアンスがオフラインであることを確認します。 -1. 交換用の {% data variables.product.prodname_ghe_server %} アプライアンスでネットワーク設定を手動設定します。 ネットワーク設定はバックアップスナップショットから除外され、`ghe-restore` で上書きされません。 -1. もともとのアプライアンスと同じ {% data variables.product.prodname_actions %} 外部ストレージ構成を使用するように交換アプライアンスを構成するには、新しいアプライアンスから、必須のパラメーターを `ghe-config` コマンドで設定します。 - - - Azure Blob Storage - ```shell - ghe-config secrets.actions.storage.blob-provider "azure" - ghe-config secrets.actions.storage.azure.connection-string "_Connection_String_" - ``` - - Amazon S3 - ```shell - ghe-config secrets.actions.storage.blob-provider "s3" - ghe-config secrets.actions.storage.s3.bucket-name "_S3_Bucket_Name" - ghe-config secrets.actions.storage.s3.service-url "_S3_Service_URL_" - ghe-config secrets.actions.storage.s3.access-key-id "_S3_Access_Key_ID_" - ghe-config secrets.actions.storage.s3.access-secret "_S3_Access_Secret_" - ``` - - 必要に応じて、S3 強制パススタイルを有効にするには、次のコマンドを入力します。 - ```shell - ghe-config secrets.actions.storage.s3.force-path-style true - ``` - +However, not all the data for {% data variables.product.prodname_actions %} is included in these backups. {% data reusables.actions.enterprise-storage-ha-backups %} -1. 交換用アプライアンスで {% data variables.product.prodname_actions %} を有効化します。 これにより、交換用アプライアンスが {% data variables.product.prodname_actions %} の同じ外部ストレージに接続されます。 +## Restoring a backup of {% data variables.product.product_name %} when {% data variables.product.prodname_actions %} is enabled - ```shell - ghe-config app.actions.enabled true - ghe-config-apply - ``` +To restore a backup of {% data variables.product.product_location %} with {% data variables.product.prodname_actions %}, you must manually configure network settings and external storage on the destination instance before you restore your backup from {% data variables.product.prodname_enterprise_backup_utilities %}. -1. {% data variables.product.prodname_actions %} が構成され、有効になったら、`ghe-restore` コマンドを使い、残りのデータをバックアップから復元します。 詳しくは、「[バックアップの復元](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)」を参照してください。 -1. セルフホストランナーを交換用アプライアンスに再登録します。 詳細については、「[セルフホステッド ランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners)」をご覧ください。 +1. Confirm that the source instance is offline. +1. Manually configure network settings on the replacement {% data variables.product.prodname_ghe_server %} instance. Network settings are excluded from the backup snapshot, and are not overwritten by `ghe-restore`. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)." +1. SSH into the destination instance. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." -{% data variables.product.prodname_ghe_server %} のバックアップと復元について詳しくは、「[アプライアンスでバックアップを構成する](/admin/configuration/configuring-backups-on-your-appliance)」を参照してください。 + ```shell{:copy} + $ ssh -p 122 admin@HOSTNAME + ``` +1. Configure the destination instance to use the same external storage service for {% data variables.product.prodname_actions %} as the source instance by entering one of the following commands. +{% indented_data_reference reusables.actions.configure-storage-provider-platform-commands spaces=3 %} +{% data reusables.actions.configure-storage-provider %} +1. To prepare to enable {% data variables.product.prodname_actions %} on the destination instance, enter the following command. + + ```shell{:copy} + ghe-config app.actions.enabled true + ``` +{% data reusables.actions.apply-configuration-and-enable %} +1. After {% data variables.product.prodname_actions %} is configured and enabled, to restore the rest of the data from the backup, use the `ghe-restore` command. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)." +1. Re-register your self-hosted runners on the destination instance. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md index c1e82392a8..6fa069a0f2 100644 --- a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md +++ b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md @@ -1,53 +1,157 @@ --- -title: ステージングインスタンスのセットアップ -intro: '別の分離された環境に {% data variables.product.product_name %} インスタンスを設定し、そのインスタンスを使って変更の検証とテストを行うことができます。' +title: Setting up a staging instance +intro: 'You can set up a {% data variables.product.product_name %} instance in a separate, isolated environment, and use the instance to validate and test changes.' redirect_from: - /enterprise/admin/installation/setting-up-a-staging-instance - /admin/installation/setting-up-a-staging-instance versions: - ghes: '*' + ghes: "*" type: how_to topics: - Enterprise - Infrastructure - Upgrades shortTitle: Set up a staging instance -ms.openlocfilehash: 86006b3dd1fcdd7a7139f35934cafce1f208c8bb -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147065363' +miniTocMaxHeadingLevel: 3 --- -## ステージング インスタンスについて -{% data variables.product.company_short %} では、{% data variables.product.product_location %} の構成のバックアップ、更新、または変更をテストするために別の環境を設定することを推奨しています。 運用システムから分離する必要があるこの環境は、ステージング環境と呼ばれます。 +## About staging instances -たとえば、データの損失から保護するために、運用インスタンスのバックアップを定期的に検証できます。 ステージング環境の別の {% data variables.product.product_name %} インスタンスに、運用データのバックアップを定期的に復元できます。 このステージング インスタンスでは、{% data variables.product.product_name %} の最新の機能リリースへのアップグレードをテストすることもできます。 +{% data variables.product.company_short %} recommends that you set up a separate environment to test backups, updates, or changes to the configuration for {% data variables.product.product_location %}. This environment, which you should isolate from your production systems, is called a staging environment. + +For example, to protect against loss of data, you can regularly validate the backup of your production instance. You can regularly restore the backup of your production data to a separate {% data variables.product.product_name %} instance in a staging environment. On this staging instance, you could also test the upgrade to the latest feature release of {% data variables.product.product_name %}. {% tip %} -**ヒント:** ステージング インスタンスを本番容量で使用しない限り、既存の {% data variables.product.prodname_enterprise %} ライセンス ファイルを再利用できます。 +**Tip:** You may reuse your existing {% data variables.product.prodname_enterprise %} license file as long as the staging instance is not used in a production capacity. {% endtip %} -## ステージング環境に関する考慮事項 +## Considerations for a staging environment -{% data variables.product.product_name %} を十分にテストし、運用環境とできるだけ似た環境を再作成するには、インスタンスと対話する外部システムを検討してください。 たとえば、ステージング環境では次をテストできます。 +To thoroughly test {% data variables.product.product_name %} and recreate an environment that's as similar to your production environment as possible, consider the external systems that interact with your instance. For example, you may want to test the following in your staging environment. -- 認証 (特に SAML などの外部認証プロバイダーを使用する場合) -- 外部のチケットシステムとの統合 -- 継続的インテグレーションサーバとの統合 -- {% data variables.product.prodname_enterprise_api %}を利用する外部のスクリプトあるいはソフトウェア -- メール通知のための外部のSMTPサーバ +- Authentication, especially if you use an external authentication provider like SAML +- Integration with an external ticketing system +- Integration with a continuous integration server +- External scripts or software that use the {% data variables.product.prodname_enterprise_api %} +- External SMTP server for email notifications -## ステージングインスタンスのセットアップ +## Setting up a staging instance -1. {% data variables.product.prodname_enterprise_backup_utilities %}を使って本番インスタンスをバックアップしてください。 詳細については、「[アプライアンスでバックアップを構成する](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#about-github-enterprise-server-backup-utilities)」の「{% data variables.product.prodname_enterprise_backup_utilities %} について」セクションを参照してください。 -2. 新しいインスタンスをステージング環境として動作するようにセットアップしてください。 ステージングインスタンスのプロビジョニングとインストールについては、本番インスタンスと同じガイドが利用できます。 詳細については、「[{% data variables.product.prodname_ghe_server %} インスタンスをセットアップする](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)」を参照してください。 -3. 必要に応じて、テスト環境で {% data variables.product.prodname_actions %} 機能をテストする場合は、ログとストレージに関する考慮事項を確認してください。 詳細については、「[ステージング環境を使用する](/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment)」を参照してください。 -4. バックアップをステージングインスタンスにリストアしてください。 詳細については、「[アプライアンスでバックアップを構成する](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#restoring-a-backup)」の「バックアップの復元」セクションを参照してください。 +You can set up a staging instance from scratch and configure the instance however you like. For more information, see "[Setting up a {% data variables.product.product_name %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)" and "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)." -## 参考資料 +Alternatively, you can create a staging instance that reflects your production configuration by restoring a backup of your production instance to the staging instance. -- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」 +1. [Back up your production instance](#1-back-up-your-production-instance). +2. [Set up a staging instance](#2-set-up-a-staging-instance). +3. [Configure {% data variables.product.prodname_actions %}](#3-configure-github-actions). +4. [Configure {% data variables.product.prodname_registry %}](#4-configure-github-packages). +5. [Restore your production backup](#5-restore-your-production-backup). +6. [Review the instance's configuration](#6-review-the-instances-configuration). +7. [Apply the instance's configuration](#7-apply-the-instances-configuration). + +### 1. Back up your production instance + +If you want to test changes on an instance that contains the same data and configuration as your production instance, back up the data and configuration from the production instance using {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)." + +{% warning %} + +**Warning**: If you use {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} in production, your backup will include your production configuration for external storage. To avoid potential loss of data by writing to your production storage from your staging instance, you must configure each feature in steps 3 and 4 before you restore your backup. + +{% endwarning %} + +### 2. Set up a staging instance + +Set up a new instance to act as your staging environment. You can use the same guides for provisioning and installing your staging instance as you did for your production instance. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)." + +If you plan to restore a backup of your production instance, continue to the next step. Alternatively, you can configure the instance manually and skip the following steps. + +### 3. Configure {% data variables.product.prodname_actions %} + +Optionally, if you use {% data variables.product.prodname_actions %} on your production instance, configure the feature on the staging instance before restoring your production backup. If you don't use {% data variables.product.prodname_actions %}, skip to "[4. Configure {% data variables.product.prodname_registry %}](#4-configure-github-packages)." + +{% warning %} + +**Warning**: If you don't configure {% data variables.product.prodname_actions %} on the staging instance before restoring your production backup, your staging instance will use your production instance's external storage, which could result in loss of data. We strongly recommended that you use different external storage for your staging instance. For more information, see "[Using a staging environment](/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment)." + +{% endwarning %} + +{% data reusables.enterprise_installation.ssh-into-staging-instance %} +1. To configure the staging instance to use an external storage provider for {% data variables.product.prodname_actions %}, enter one of the following commands. +{% indented_data_reference reusables.actions.configure-storage-provider-platform-commands spaces=3 %} +{% data reusables.actions.configure-storage-provider %} +1. To prepare to enable {% data variables.product.prodname_actions %} on the staging instance, enter the following command. + + ```shell{:copy} + ghe-config app.actions.enabled true + ``` + +### 4. Configure {% data variables.product.prodname_registry %} + +Optionally, if you use {% data variables.product.prodname_registry %} on your production instance, configure the feature on the staging instance before restoring your production backup. If you don't use {% data variables.product.prodname_registry %}, skip to "[5. Restore your production backup](#5-restore-your-production-backup)." + +{% warning %} + +**Warning**: If you don't configure {% data variables.product.prodname_actions %} on the staging instance before restoring your production backup, your staging instance will use your production instance's external storage, which could result in loss of data. We strongly recommended that you use different external storage for your staging instance. + +{% endwarning %} + +1. Review the backup you will restore to the staging instance. + - If you took the backup with {% data variables.product.prodname_enterprise_backup_utilities %} 3.5 or later, the backup includes the configuration for {% data variables.product.prodname_registry %}. Continue to the next step. + - If you took the backup with {% data variables.product.prodname_enterprise_backup_utilities %} 3.4 or earlier, configure {% data variables.product.prodname_registry %} on the staging instance. For more information, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." +{% data reusables.enterprise_installation.ssh-into-staging-instance %} +1. Configure the external storage connection by entering the following commands, replacing the placeholder values with actual values for your connection. + - Azure Blob Storage: + + ```shell{:copy} + ghe-config secrets.packages.blob-storage-type "azure" + ghe-config secrets.packages.azure-container-name "AZURE CONTAINER NAME" + ghe-config secrets.packages.azure-connection-string "CONNECTION STRING" + ``` + - Amazon S3: + + ```shell{:copy} + ghe-config secrets.packages.blob-storage-type "s3" + ghe-config secrets.packages.service-url "S3 SERVICE URL" + ghe-config secrets.packages.s3-bucket "S3 BUCKET NAME" + ghe-config secrets.packages.aws-access-key "S3 ACCESS KEY ID" + ghe-config secrets.packages.aws-secret-key "S3 ACCESS SECRET" + ``` +1. To prepare to enable {% data variables.product.prodname_registry %} on the staging instance, enter the following command. + + ```shell{:copy} + ghe-config app.packages.enabled true + ``` + +### 5. Restore your production backup + +Use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)." + +If the staging instance is already configured and you're about to overwrite settings, certificate, and license data, add the `-c` option to the command. For more information about the option, see [Using the backup and restore commands](https://github.com/github/backup-utils/blob/master/docs/usage.md#restoring-settings-tls-certificate-and-license) in the {% data variables.product.prodname_enterprise_backup_utilities %} documentation. + +### 6. Review the instance's configuration + +To access the staging instance using the same hostname, update your local hosts file to resolve the staging instance's hostname by IP address by editing the `/etc/hosts` file in macOS or Linux, or the `C:\Windows\system32\drivers\etc` file in Windows. + +{% note %} + +**Note**: Your staging instance must be accessible from the same hostname as your production instance. Changing the hostname for {% data variables.product.product_location %} is not supported. For more information, see "[Configuring a hostname](/admin/configuration/configuring-network-settings/configuring-a-hostname)." + +{% endnote %} + +Then, review the staging instance's configuration in the {% data variables.enterprise.management_console %}. For more information, see "[Accessing the {% data variables.enterprise.management_console %}](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)." + +{% warning %} + +**Warning**: If you configured {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} for the staging instance, to avoid overwriting production data, ensure that the external storage configuration in the {% data variables.enterprise.management_console %} does not match your production instance. + +{% endwarning %} + +### 7. Apply the instance's configuration + +To apply the configuration from the {% data variables.enterprise.management_console %}, click **Save settings**. + +## Further reading + +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" diff --git a/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md b/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md index f0ef5e37da..63db7352b5 100644 --- a/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md +++ b/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md @@ -150,7 +150,7 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | Keyboard shortcut | Description |-----------|------------ -|⌘+f (Mac) or Ctrl+f (Windows/Linux) | Focus filter field +|Command+f (Mac) or Ctrl+f (Windows/Linux) | Focus filter field |← | Move cell focus to the left |→ | Move cell focus to the right |↑ | Move cell focus up @@ -162,7 +162,7 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |-----------|------------ |Enter | Toggle edit mode for the focused cell |Escape | Cancel editing for the focused cell -|⌘+Shift+\ (Mac) or Ctrl+Shift+\ (Windows/Linux) | Open row actions menu +|Command+Shift+\ (Mac) or Ctrl+Shift+\ (Windows/Linux) | Open row actions menu |Shift+Space | Select item |Space | Open selected item |e | Archive selected items diff --git a/translations/ja-JP/content/index.md b/translations/ja-JP/content/index.md index 5385321f93..91ea171895 100644 --- a/translations/ja-JP/content/index.md +++ b/translations/ja-JP/content/index.md @@ -75,6 +75,10 @@ childGroups: octicon: ShieldLockIcon children: - code-security + - code-security/supply-chain-security + - code-security/dependabot + - code-security/code-scanning + - code-security/secret-scanning - name: Client apps octicon: DeviceMobileIcon children: diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md index b628d23e81..58f47d8e9d 100644 --- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md @@ -1,6 +1,6 @@ --- -title: Organization のセキュリティおよび分析設定を管理する -intro: '{% data variables.product.prodname_dotcom %} 上の Organization のプロジェクトでコードを保護し分析する機能を管理できます。' +title: Managing security and analysis settings for your organization +intro: 'You can control features that secure and analyze the code in your organization''s projects on {% data variables.product.prodname_dotcom %}.' permissions: Organization owners can manage security and analysis settings for repositories in the organization. redirect_from: - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization @@ -15,115 +15,156 @@ topics: - Organizations - Teams shortTitle: Manage security & analysis -ms.openlocfilehash: 83104f606266279a239c5173e838c9241832fb84 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147063211' --- -## セキュリティおよび分析設定の管理について -{% data variables.product.prodname_dotcom %} を使用して、Organization のリポジトリを保護できます。 Organization でメンバーが作成する既存または新規のリポジトリすべてについて、セキュリティおよび分析機能を管理できます。 {% ifversion ghec %}{% data variables.product.prodname_GH_advanced_security %} のライセンスを持っている場合は、これらの機能へのアクセスを管理することもできます。 {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}{% data variables.product.prodname_GH_advanced_security %}のライセンス付きで{% data variables.product.prodname_ghe_cloud %}を使用するOrganizationは、それらの機能へのアクセスも管理できます。 詳細については、[{% data variables.product.prodname_ghe_cloud %} ドキュメント](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)を参照してください。{% endif %} +## About management of security and analysis settings -{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} {% data reusables.security.security-and-analysis-features-enable-read-only %} +{% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. {% ifversion ghec %}If you have a license for {% data variables.product.prodname_GH_advanced_security %} then you can also manage access to these features. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can also manage access to these features. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).{% endif %} -## セキュリティと分析の設定を表示する +{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +{% data reusables.security.security-and-analysis-features-enable-read-only %} -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security-and-analysis %} +## Displaying the security and analysis settings -表示されるページでは、Organization 内のリポジトリのすべてのセキュリティおよび分析機能を有効化または無効化にできます。 +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.organizations.security-and-analysis %} -{% ifversion ghec %}Organization が {% data variables.product.prodname_GH_advanced_security %} のライセンスを持つ Enterprise に属している場合、ページには {% data variables.product.prodname_advanced_security %} 機能を有効化または無効化するオプションも含まれます。 {% data variables.product.prodname_GH_advanced_security %} を使用するリポジトリは、ページの下部に一覧表示されます。{% endif %} +The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. -{% ifversion ghes %}{% data variables.product.prodname_GH_advanced_security %} のライセンスを持っている場合、ページには {% data variables.product.prodname_advanced_security %} 機能を有効化または無効化するオプションも含まれます。 {% data variables.product.prodname_GH_advanced_security %} を使用するリポジトリは、ページの下部に一覧表示されます。{% endif %} +{% ifversion ghec %}If your organization belongs to an enterprise with a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %} -{% ifversion ghae %}このページには、{% data variables.product.prodname_advanced_security %} 機能を有効または無効にするオプションも含まれています。 {% data variables.product.prodname_GH_advanced_security %} を使用するリポジトリは、ページの下部に一覧表示されます。{% endif %} +{% ifversion ghes %}If you have a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %} -## 既存のすべてのリポジトリの機能を有効または無効にする +{% ifversion ghae %}The page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %} -すべてのリポジトリの機能を有効化または無効化できます。 {% ifversion fpt or ghec %}変更が Organization 内のリポジトリに与える影響は、リポジトリの可視性によって決まります。 +## Enabling or disabling a feature for all existing repositories -- **依存関係グラフ** - この機能はパブリック リポジトリに対して常に有効になっているため、変更はプライベート リポジトリにのみ影響します。 -- **{% data variables.product.prodname_dependabot_alerts %}** - 変更はすべてのリポジトリに影響します。 -- **{% data variables.product.prodname_dependabot_security_updates %}** - 変更はすべてのリポジトリに影響します。 +You can enable or disable features for all repositories. +{% ifversion fpt or ghec %}The impact of your changes on repositories in your organization is determined by their visibility: + +- **Dependency graph** - Your changes affect only private repositories because the feature is always enabled for public repositories. +- **{% data variables.product.prodname_dependabot_alerts %}** - Your changes affect all repositories. +- **{% data variables.product.prodname_dependabot_security_updates %}** - Your changes affect all repositories. {%- ifversion ghec %} -- **{% data variables.product.prodname_GH_advanced_security %}** - {% data variables.product.prodname_GH_advanced_security %} および関連機能は常にパブリック リポジトリに対して有効になっているため、変更はプライベート リポジトリにのみ影響します。 -- **{% data variables.product.prodname_secret_scanning_caps %}** - 変更は、{% data variables.product.prodname_GH_advanced_security %}も有効になっているリポジトリにのみ影響します。 このオプションは、{% data variables.product.prodname_secret_scanning_GHAS %}が有効になっているかどうかを制御します。 {% data variables.product.prodname_secret_scanning_partner_caps %}は、すべてのパブリックリポジトリ上で常に実行されます。 +- **{% data variables.product.prodname_GH_advanced_security %}** - Your changes affect only private repositories because {% data variables.product.prodname_GH_advanced_security %} and the related features are always enabled for public repositories. +- **{% data variables.product.prodname_secret_scanning_caps %}** - Your changes affect repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. This option controls whether or not {% data variables.product.prodname_secret_scanning_GHAS %} is enabled. {% data variables.product.prodname_secret_scanning_partner_caps %} always runs on all public repositories. {% endif %} {% endif %} {% data reusables.advanced-security.note-org-enable-uses-seats %} -1. 組織のセキュリティと分析の設定に移動します。 詳細については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。 -2. [Code security and analysis] の下で機能の右にある **[Disable all]** または **[Enable all]** をクリックします。 {% ifversion ghes or ghec %}{% data variables.product.prodname_GH_advanced_security %} ライセンスに空きシートがない場合、"{% data variables.product.prodname_GH_advanced_security %}" のコントロールは無効になります。{% endif %} {% ifversion fpt %}![[セキュリティと分析の構成] 機能の [すべて有効にする] または [すべて無効にする] ボタン](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-fpt.png){% endif %} {% ifversion ghec %}![[セキュリティと分析の構成] 機能の [すべて有効にする] または [すべて無効にする] ボタン](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-ghec.png){% endif %} {% ifversion ghes > 3.2 %}![[セキュリティと分析の構成] 機能の [すべて有効にする] または [すべて無効にする] ボタン](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png){% endif %} {% ifversion ghes = 3.2 %}![[セキュリティと分析の構成] 機能の [すべて有効にする] または [すべて無効にする] ボタン](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png){% endif %} +{% ifversion ghes or ghec or ghae %} +{% note %} + +**Note:** If you encounter an error that reads "GitHub Advanced Security cannot be enabled because of a policy setting for the organization," contact your enterprise admin and ask them to change the GitHub Advanced Security policy for your enterprise. For more information, see "[Enforcing policies for Advanced Security in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)." +{% endnote %} +{% endif %} + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +2. Under "Code security and analysis", to the right of the feature, click **Disable all** or **Enable all**. {% ifversion ghes or ghec %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if you have no available seats in your {% data variables.product.prodname_GH_advanced_security %} license.{% endif %} + {% ifversion fpt %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-fpt.png) + {% endif %} + {% ifversion ghec %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-ghec.png) + {% endif %} + {% ifversion ghes > 3.2 %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png) + {% endif %} + {% ifversion ghes = 3.2 %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png) + {% endif %} - {% ifversion ghae %}![[セキュリティと分析の構成] 機能の [すべて有効にする] または [すべて無効にする] ボタン](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png){% endif %} {% ifversion fpt or ghec %} -3. オプションで、Organization の新しいリポジトリに対して機能をデフォルトで有効にすることもできます。 - {% ifversion fpt or ghec %}![新しいリポジトリの [既定で有効にする] オプション](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png){% endif %} + {% ifversion ghae %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png) + {% endif %} + {% ifversion fpt or ghec %} +3. Optionally, enable the feature by default for new repositories in your organization. + {% ifversion fpt or ghec %} + !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) + {% endif %} - {% endif %} {% ifversion fpt or ghec %} -4. **[機能の無効化]** または **[機能の有効化]** をクリックし、Organization のすべてのリポジトリに対してこの機能を無効または有効にします。 - {% ifversion fpt or ghec %}![機能を無効または有効にするボタン](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png){% endif %} + {% endif %} + {% ifversion fpt or ghec %} +4. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. + {% ifversion fpt or ghec %} + ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + {% endif %} - {% endif %} {% ifversion ghae or ghes %} -3. **[すべて有効にする]/[すべて無効にする]** または **[対象リポジトリの有効化]/[対象リポジトリの無効化]** をクリックして、変更を確定します。 - ![Organization 内の適格なすべてのリポジトリの機能を有効化するボタン](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png) {% endif %} + {% endif %} + {% ifversion ghae or ghes %} +5. Click **Enable/Disable all** or **Enable/Disable for eligible repositories** to confirm the change. + ![Button to enable feature for all the eligible repositories in the organization](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png) + {% endif %} {% data reusables.security.displayed-information %} -## 新しいリポジトリが追加されたときに機能を自動的に有効化または無効化する +## Enabling or disabling a feature automatically when new repositories are added -1. 組織のセキュリティと分析の設定に移動します。 詳細については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。 -2. "Code security and analysis（コードのセキュリティと分析）"の下で、機能の右から、Organizationの新しいリポジトリ{% ifversion fpt or ghec %}、もしくはすべての新しいプライベートリポジトリ{% endif %}でデフォルトでこの機能を有効化もしくは無効化してください。 - {% ifversion fpt or ghec %}![新しいリポジトリの機能を有効にするためのチェックボックスのスクリーンショット](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png){% endif %} {% ifversion ghes > 3.2 %}![新しいリポジトリの機能を有効にするためのチェックボックスのスクリーンショット](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png){% endif %} {% ifversion ghes = 3.2 %}![新しいリポジトリの機能を有効にするためのチェックボックスのスクリーンショット](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png){% endif %} {% ifversion ghae %}![新しいリポジトリの機能を有効にするためのチェックボックスのスクリーンショット](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png){% endif %} +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +2. Under "Code security and analysis", to the right of the feature, enable or disable the feature by default for new repositories{% ifversion fpt or ghec %}, or all new private repositories,{% endif %} in your organization. + {% ifversion fpt or ghec %} + ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) + {% endif %} + {% ifversion ghes > 3.2 %} + ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) + {% endif %} + {% ifversion ghes = 3.2 %} + ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) + {% endif %} + {% ifversion ghae %} + ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png) + {% endif %} {% ifversion fpt or ghec or ghes > 3.2 %} -## {% data variables.product.prodname_dependabot %} のプライベート依存関係へのアクセスを許可する +## Allowing {% data variables.product.prodname_dependabot %} to access private dependencies -{% data variables.product.prodname_dependabot %} は、プロジェクト内の古い依存関係参照をチェックし、それらを更新するためのプルリクエストを自動的に生成できます。 これを行うには、{% data variables.product.prodname_dependabot %} がすべてのターゲット依存関係ファイルにアクセスできる必要があります。 通常、1 つ以上の依存関係にアクセスできない場合、バージョン更新は失敗します。 詳細については、「[{% data variables.product.prodname_dependabot %} のバージョン アップデートについて](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。 +{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to all of the targeted dependency files. Typically, version updates will fail if one or more dependencies are inaccessible. For more information, see "[About {% data variables.product.prodname_dependabot %} version updates](/github/administering-a-repository/about-dependabot-version-updates)." -デフォルトでは、{% data variables.product.prodname_dependabot %} はプライベートリポジトリまたはプライベートパッケージレジストリにある依存関係を更新できません。 ただし、依存関係が、その依存関係を使用するプロジェクトと同じ Organization 内のプライベート {% data variables.product.prodname_dotcom %} リポジトリにある場合は、ホストリポジトリへのアクセスを許可することで、{% data variables.product.prodname_dependabot %} がバージョンを正常に更新できるようにすることができます。 +By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories or private package registries. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. -コードがプライベートレジストリ内のパッケージに依存している場合は、リポジトリレベルでこれを設定することにより、{% data variables.product.prodname_dependabot %} がこれらの依存関係のバージョンを更新できるようにすることができます。 これを行うには、リポジトリの _dependabot.yml_ ファイルに認証の詳細を追加します。 詳細については、「[dependabot.yml ファイルの構成オプション](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)」を参照してください。 +If your code depends on packages in a private registry, you can allow {% data variables.product.prodname_dependabot %} to update the versions of these dependencies by configuring this at the repository level. You do this by adding authentication details to the _dependabot.yml_ file for the repository. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." -{% data variables.product.prodname_dependabot %} がプライベート {% data variables.product.prodname_dotcom %} リポジトリにアクセスできるようにするには： +To allow {% data variables.product.prodname_dependabot %} to access a private {% data variables.product.prodname_dotcom %} repository: -1. 組織のセキュリティと分析の設定に移動します。 詳細については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。 -1. [{% data variables.product.prodname_dependabot %} プライベート リポジトリ アクセス] で、 **[プライベート リポジトリの追加]** または **[内部およびプライベート リポジトリの追加]** をクリックします。 - ![[リポジトリの追加] ボタン](/assets/images/help/organizations/dependabot-private-repository-access.png) -1. 許可するリポジトリの名前の入力を開始します。 - ![フィルタされたドロップダウンを持つリポジトリ検索フィールド](/assets/images/help/organizations/dependabot-private-repo-choose.png) -1. 許可するリポジトリをクリックします。 +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. Under "{% data variables.product.prodname_dependabot %} private repository access", click **Add private repositories** or **Add internal and private repositories**. + ![Add repositories button](/assets/images/help/organizations/dependabot-private-repository-access.png) +1. Start typing the name of the repository you want to allow. + ![Repository search field with filtered dropdown](/assets/images/help/organizations/dependabot-private-repo-choose.png) +1. Click the repository you want to allow. -1. あるいは、リストからリポジトリを差k除するには、リポジトリの右の{% octicon "x" aria-label="The X icon" %}をクリックします。 - ![リポジトリを削除するための [X] ボタン](/assets/images/help/organizations/dependabot-private-repository-list.png){% endif %} +1. Optionally, to remove a repository from the list, to the right of the repository, click {% octicon "x" aria-label="The X icon" %}. + !["X" button to remove a repository](/assets/images/help/organizations/dependabot-private-repository-list.png) +{% endif %} {% ifversion ghes or ghec %} -## Organization 内の個々のリポジトリから {% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除する +## Removing access to {% data variables.product.prodname_GH_advanced_security %} from individual repositories in an organization -リポジトリの {% data variables.product.prodname_GH_advanced_security %} 機能へのアクセスは、[設定] タブで管理できます。詳細については、「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。 ただし、Organization の [Settings] タブから、リポジトリの {% data variables.product.prodname_GH_advanced_security %} 機能を無効にすることもできます。 +You can manage access to {% data variables.product.prodname_GH_advanced_security %} features for a repository from its "Settings" tab. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." However, you can also disable {% data variables.product.prodname_GH_advanced_security %} features for a repository from the "Settings" tab for the organization. -1. 組織のセキュリティと分析の設定に移動します。 詳細については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。 -1. {% data variables.product.prodname_GH_advanced_security %} が有効になっている Organization 内のすべてのリポジトリのリストを表示するには、「{% data variables.product.prodname_GH_advanced_security %} リポジトリ」セクションまでスクロールします。 - ![[{% data variables.product.prodname_GH_advanced_security %} リポジトリ] セクション](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png)テーブルには、各リポジトリの一意のコミッターがリストされています。 これは、{% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除することによりライセンスで解放できるシートの数です。 詳細については、「[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)」(GitHub Advanced Security の課金について) を参照してください。 -1. リポジトリから {% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除し、リポジトリ固有のコミッターが使用するシートを解放するには、隣接する {% octicon "x" aria-label="X symbol" %} をクリックします。 -1. 確認ダイアログで、 **[リポジトリの削除]** をクリックして、{% data variables.product.prodname_GH_advanced_security %} の機能へのアクセスを削除します。 +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. To see a list of all the repositories in your organization with {% data variables.product.prodname_GH_advanced_security %} enabled, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section. + ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) + The table lists the number of unique committers for each repository. This is the number of seats you could free up on your license by removing access to {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)." +1. To remove access to {% data variables.product.prodname_GH_advanced_security %} from a repository and free up seats used by any committers that are unique to the repository, click the adjacent {% octicon "x" aria-label="X symbol" %}. +1. In the confirmation dialog, click **Remove repository** to remove access to the features of {% data variables.product.prodname_GH_advanced_security %}. {% note %} -**注:** リポジトリの {% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除する場合は、影響を受ける開発チームと連絡を取り、変更が意図されたものかを確認する必要があります。 これにより、失敗したコードスキャンの実行をデバッグすることに時間を費すことがなくなります。 +**Note:** If you remove access to {% data variables.product.prodname_GH_advanced_security %} for a repository, you should communicate with the affected development team so that they know that the change was intended. This ensures that they don't waste time debugging failed runs of code scanning. {% endnote %} {% endif %} -## 参考資料 +## Further reading -- 「[リポジトリの保護](/code-security/getting-started/securing-your-repository)」{% ifversion not fpt %} -- 「[シークレット スキャンについて](/github/administering-a-repository/about-secret-scanning)」{% endif %}{% ifversion not ghae %} -- [依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph){% endif %} -- [サプライ チェーンのセキュリティについて](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security) +- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %} +- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %} +- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %} +- "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)" diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md index 92900222ad..dff4c98d4d 100644 --- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md +++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md @@ -30,7 +30,7 @@ Prerequisites for repository transfers: - When you transfer a repository that you own to another personal account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %} - To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization. - The target account must not have a repository with the same name, or a fork in the same network. -- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghes < 3.7 %} +- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghes < 3.7 or ghae %} - Internal repositories can't be transferred.{% endif %} - Private forks can't be transferred. diff --git a/translations/log/msft-ja-resets.csv b/translations/log/msft-ja-resets.csv index 2b21018c94..c1e0bdd8ea 100644 --- a/translations/log/msft-ja-resets.csv +++ b/translations/log/msft-ja-resets.csv @@ -252,6 +252,7 @@ translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifi translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags +translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,broken liquid tags translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md,broken liquid tags translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,broken liquid tags translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error @@ -299,18 +300,20 @@ translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows translations/ja-JP/content/actions/using-workflows/reusing-workflows.md,rendering error translations/ja-JP/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md,rendering error translations/ja-JP/content/actions/using-workflows/triggering-a-workflow.md,rendering error -translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md,broken liquid tags +translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md,rendering error translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,broken liquid tags translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md,rendering error translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error +translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md,broken liquid tags translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,rendering error 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,rendering error translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md,rendering error translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,broken liquid tags translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,rendering error +translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md,broken liquid tags translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,rendering error translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md,broken liquid tags @@ -469,6 +472,7 @@ translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md,broken liquid tags translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error +translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,broken liquid tags translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md,rendering error translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md,rendering error @@ -511,7 +515,7 @@ translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your- translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md,rendering error translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md,rendering error translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error -translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,broken liquid tags +translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md,rendering error translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,rendering error translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error From f8e01c45745279c474a55e8f22894da4a120daad Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Wed, 12 Oct 2022 10:49:30 -0700 Subject: [PATCH 8/8] New translation batch for pt (#31649) --- translations/log/msft-pt-resets.csv | 6 +- .../personalizing-your-profile.md | 204 ++++++++++-------- .../security-hardening-for-github-actions.md | 2 +- ...rise-server-with-github-actions-enabled.md | 65 +++--- .../setting-up-a-staging-instance.md | 158 +++++++++++--- .../using-github/keyboard-shortcuts.md | 4 +- translations/pt-BR/content/index.md | 4 + ...analysis-settings-for-your-organization.md | 171 +++++++++------ .../transferring-a-repository.md | 2 +- 9 files changed, 391 insertions(+), 225 deletions(-) diff --git a/translations/log/msft-pt-resets.csv b/translations/log/msft-pt-resets.csv index cd4a45228b..9a3733877a 100644 --- a/translations/log/msft-pt-resets.csv +++ b/translations/log/msft-pt-resets.csv @@ -240,6 +240,7 @@ translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifi translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags +translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,broken liquid tags translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md,broken liquid tags translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,broken liquid tags translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md,broken liquid tags @@ -298,6 +299,7 @@ translations/pt-BR/content/admin/configuration/configuring-your-enterprise/confi translations/pt-BR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md,broken liquid tags translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error +translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md,broken liquid tags translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,rendering error translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md,rendering error translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error @@ -307,6 +309,7 @@ translations/pt-BR/content/admin/identity-and-access-management/using-enterprise translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,broken liquid tags translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md,broken liquid tags translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,broken liquid tags +translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md,broken liquid tags translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,rendering error translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md,broken liquid tags @@ -477,6 +480,7 @@ translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-y translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md,broken liquid tags translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error +translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,broken liquid tags translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md,rendering error translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md,rendering error @@ -518,7 +522,7 @@ translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your- translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error -translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,broken liquid tags +translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md,rendering error translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,rendering error translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md index f4fa565ae4..850fdd4282 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md @@ -1,6 +1,6 @@ --- -title: Personalizar seu perfil -intro: 'É possível compartilhar informações sobre você mesmo com outros usuários do {% data variables.product.product_name %} definindo uma imagem e adicionando uma bio ao seu perfil.' +title: Personalizing your profile +intro: 'You can share information about yourself with other {% data variables.product.product_name %} users by setting a profile picture and adding a bio to your profile.' redirect_from: - /articles/adding-a-bio-to-your-profile - /articles/setting-your-profile-picture @@ -18,156 +18,186 @@ versions: topics: - Profiles shortTitle: Personalize -ms.openlocfilehash: c12fccd91144428fe9aad2f01d2c0b0941fdd4d4 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146681050' --- -## Alterar sua imagem de perfil +## Changing your profile picture -Sua imagem de perfil ajuda a identificá-lo no {% data variables.product.product_name %} em pull requests, comentários, páginas de contribuições e gráficos. +Your profile picture helps identify you across {% data variables.product.product_name %} in pull requests, comments, contributions pages, and graphs. -Ao se inscrever em uma conta, o {% data variables.product.product_name %} fornece a você uma "identicon" gerada aleatoriamente. [Seu identicon](https://github.com/blog/1586-identicons) é gerado com base em um hash da sua ID de usuário, portanto, não há como controlar a cor ou o padrão. É possível substituir sua identicon por uma imagem que represente você. +When you sign up for an account, {% data variables.product.product_name %} provides you with a randomly generated "identicon". [Your identicon](https://github.com/blog/1586-identicons) generates from a hash of your user ID, so there's no way to control its color or pattern. You can replace your identicon with an image that represents you. {% note %} -**Observação{% ifversion ghec %}s{% endif %}** : {% ifversion ghec %} +**Note{% ifversion ghec %}s{% endif %}**: {% ifversion ghec %} -* {% endif %}Sua imagem de perfil deve ser um arquivo PNG, JPG ou GIF com menos de 1 MB de tamanho e menos de 3000 por 3000 pixels. Para melhor qualidade de renderização, recomendamos uma imagem de aproximadamente 500 por 500 pixels. -{% ifversion ghec %}* As imagens de perfil do Gravatar não são compatíveis com {% data variables.product.prodname_emus %}.{% endif %} +* {% endif %}Your profile picture should be a PNG, JPG, or GIF file, and it must be less than 1 MB in size and smaller than 3000 by 3000 pixels. For the best quality rendering, we recommend keeping the image at about 500 by 500 pixels. +{% ifversion ghec %}* Gravatar profile pictures are not supported with {% data variables.product.prodname_emus %}.{% endif %} {% endnote %} -### Definir uma imagem de perfil +### Setting a profile picture {% data reusables.user-settings.access_settings %} -2. Em **Imagem de Perfil**, clique em {% octicon "pencil" aria-label="The edit icon" %} **Editar**. -![Editar imagem de perfil](/assets/images/help/profile/edit-profile-photo.png) -3. Clique em **Carregar uma foto...** .{% ifversion not ghae %} ![Atualizar imagem de perfil](/assets/images/help/profile/edit-profile-picture-options.png){% endif %} -3. Recorte sua imagem. Quando terminar, clique em **Definir nova imagem de perfil**. - ![Cortar a foto carregada](/assets/images/help/profile/avatar_crop_and_save.png) +2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**. +![Edit profile picture](/assets/images/help/profile/edit-profile-photo.png) +3. Click **Upload a photo...**.{% ifversion not ghae %} +![Update profile picture](/assets/images/help/profile/edit-profile-picture-options.png){% endif %} +3. Crop your picture. When you're done, click **Set new profile picture**. + ![Crop uploaded photo](/assets/images/help/profile/avatar_crop_and_save.png) -### Redefinir sua imagem de perfil para a identicon +### Resetting your profile picture to the identicon {% data reusables.user-settings.access_settings %} -2. Em **Imagem de Perfil**, clique em {% octicon "pencil" aria-label="The edit icon" %} **Editar**. -![Editar imagem de perfil](/assets/images/help/profile/edit-profile-photo.png) -3. Para reverter para o identicon, clique em **Remover foto**. {% ifversion not ghae %}Se o endereço de email estiver associado a um [Gravatar](https://en.gravatar.com/), você não poderá reverter para o identicon. Em vez disso, clique em **Reverter para Gravatar**. -![Atualizar a imagem de perfil](/assets/images/help/profile/edit-profile-picture-options.png){% endif %} +2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**. +![Edit profile picture](/assets/images/help/profile/edit-profile-photo.png) +3. To revert to your identicon, click **Remove photo**. {% ifversion not ghae %}If your email address is associated with a [Gravatar](https://en.gravatar.com/), you cannot revert to your identicon. Click **Revert to Gravatar** instead. +![Update profile picture](/assets/images/help/profile/edit-profile-picture-options.png){% endif %} -## Alterar seu nome de perfil +## Changing your profile name -Você pode alterar o nome que é exbido em seu perfil. Este nome também pode ser exibido ao lado dos comentários que você fizer em repositórios privados pertencentes a uma organização. Para obter mais informações, confira "[Gerenciando a exibição de nomes de membros em sua organização](/articles/managing-the-display-of-member-names-in-your-organization)". +You can change the name that is displayed on your profile. This name may also be displayed next to comments you make on private repositories owned by an organization. For more information, see "[Managing the display of member names in your organization](/articles/managing-the-display-of-member-names-in-your-organization)." -{% ifversion fpt or ghec %} {% note %} +{% ifversion fpt or ghec %} +{% note %} -**Observação:** se você é integrante de um {% data variables.product.prodname_emu_enterprise %}, todas as alterações no nome do seu perfil devem ser feitas por meio do seu provedor de identidade ao invés de {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} +**Note:** If you're a member of an {% data variables.product.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} -{% endnote %} {% endif %} +{% endnote %} +{% endif %} {% data reusables.user-settings.access_settings %} -2. Em "Name" (Nome), digite o nome que deseja exibir em seu perfil. - ![Campo nome em configurações de perfil](/assets/images/help/profile/name-field.png) +2. Under "Name", type the name you want to be displayed on your profile. + ![Name field in profile settings](/assets/images/help/profile/name-field.png) -## Adicionar uma bio ao seu perfil +## Adding a bio to your profile -Adicione uma bio em seu perfil para compartilhar informações sobre si mesmo com outros usuários {% data variables.product.product_name %}. Com a ajuda de [@mentions](/articles/basic-writing-and-formatting-syntax) e o emoji, você pode incluir informações sobre o local em que você trabalhou ou que trabalha atualmente, o tipo de trabalho você faz ou até mesmo o tipo de café você bebe. +Add a bio to your profile to share information about yourself with other {% data variables.product.product_name %} users. With the help of [@mentions](/articles/basic-writing-and-formatting-syntax) and emoji, you can include information about where you currently or have previously worked, what type of work you do, or even what kind of coffee you drink. {% ifversion fpt or ghes or ghec %} -Para um formulário mais longo e uma maneira mais proeminente de exibir informações personalizadas sobre você, também é possível usar um README do perfil. Para obter mais informações, confira "[Como gerenciar o LEIAME do seu perfil](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)". +For a longer-form and more prominent way of displaying customized information about yourself, you can also use a profile README. For more information, see "[Managing your profile README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)." {% endif %} {% note %} -**Observação:** se você tiver a seção de visão geral da atividade habilitada em seu perfil e você @mention uma organização da qual você é membro em sua biografia do perfil, essa organização será apresentada primeiro em sua visão geral da atividade. Para obter mais informações, veja "[Mostrando uma visão geral de sua atividade em seu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)". +**Note:** + If you have the activity overview section enabled for your profile and you @mention an organization you're a member of in your profile bio, then that organization will be featured first in your activity overview. For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)." {% endnote %} {% data reusables.user-settings.access_settings %} -2. Em **Bio**, adicione o conteúdo que você quer exibir em seu perfil. O campo bio é limitado a 160 caracteres. - ![Atualizar a bio no perfil](/assets/images/help/profile/bio-field.png) +2. Under **Bio**, add the content that you want displayed on your profile. The bio field is limited to 160 characters. + ![Update bio on profile](/assets/images/help/profile/bio-field.png) {% tip %} - **Dica:** quando você @mention uma organização, somente aquelas das quais você é membro terão o preenchimento automático. Você ainda pode @mention organizações das quais não é membro, como um empregador anterior, mas o nome da organização você não terá o preenchimento automático. + **Tip:** When you @mention an organization, only those that you're a member of will autocomplete. You can still @mention organizations that you're not a member of, like a previous employer, but the organization name won't autocomplete for you. {% endtip %} -3. Clique em **Atualizar perfil**. - ![Botão Atualizar perfil](/assets/images/help/profile/update-profile-button.png) +{% data reusables.profile.update-profile %} -## Definir um status +{% ifversion profile-time-zone %} -Você pode definir um status para exibir informações sobre sua disponibilidade atual no {% data variables.product.product_name %}. Seu status será mostrado: -- em sua página de perfil do {% data variables.product.product_name %}. -- quando as pessoas passarem o mouse em cima de seu nome de usuário ou avatar no {% data variables.product.product_name %}. -- em uma página de equipe da qual você é integrante. Para obter mais informações, confira "[Sobre as equipes](/articles/about-teams/#team-pages)". -- no painel da organização da qual você é integrante. Para obter mais informações, veja "[Sobre o painel da sua organização](/articles/about-your-organization-dashboard/)". +## Setting your location and time zone -Ao definir o seu status, você também pode informar às pessoas que sua disponibilidade é limitada no {% data variables.product.product_name %}. +You can set a location and time zone on your profile to show other people your local time. Your location and time zone will be visible: +- on your {% data variables.product.product_name %} profile page. +- when people hover over your username or avatar on {% data variables.product.product_name %}. -![O nome de usuário mencionado mostra a observação "ocupado" ao lado](/assets/images/help/profile/username-with-limited-availability-text.png) +When you view your profile, you will see your location, local time, and your time zone in relation to Universal Time Coordinated. -![O revisor solicitado mostra a observação "ocupado" ao lado do nome de usuário](/assets/images/help/profile/request-a-review-limited-availability-status.png) + ![Screenshot of the Octocat profile page emphasizing the location, local time, and time zone fields.](/assets/images/help/profile/profile-location-and-time.png) -Se você selecionar a opção "Ocupado", quando as pessoas @mention seu nome de usuário, atribuírem um problema ou uma solicitação de pull ou lhe solicitarem uma revisão, uma observação ao lado do seu nome de usuário mostrará que você está ocupado. Você também será excluído da atribuição automática de revisão para os pull requests atribuídos a qualquer equipe a que você pertença. Para obter mais informações, confira "[Gerenciando as configurações de revisão de código para sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)". +When others view your profile, they will see your location, local time, and the time difference in hours from their own local time. -1. No canto superior direito de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, clique em sua foto de perfil e clique em **Definir seu status** ou, se você já tiver um status definido, clique no status atual. - ![Botão no perfil para definir seu status](/assets/images/help/profile/set-status-on-profile.png) -2. Para adicionar um texto personalizado ao seu status, clique no campo de texto e digite uma mensagem. - ![Campo para digitar uma mensagem de status](/assets/images/help/profile/type-a-status-message.png) -3. Opcionalmente, para definir um status com emoji, clique no ícone de carinhas e selecione um emoji da lista. - ![Botão para selecionar status com emoji](/assets/images/help/profile/select-emoji-status.png) -4. Como opção, se você deseja compartilhar que tem disponibilidade limitada, selecione "Busy" (Ocupado). - ![Opção Ocupado marcada nas opções de Editar status](/assets/images/help/profile/limited-availability-status.png) -5. Use o menu suspenso **Limpar status** e selecione quando você quer que seu status expire. Caso não selecione um prazo de validade, o status será mantido até que você o limpe ou o edite. - ![Menu suspenso para escolher quando o status expira](/assets/images/help/profile/status-expiration.png) -6. Use o menu suspenso e clique na organização para a qual você deseja que seu status esteja visível. Se não selecionar uma organização, seu status será público. - ![Menu suspenso para escolher para quem seu status fica visível](/assets/images/help/profile/status-visibility.png) -7. Clique em **Definir status**. - ![Botão para definir o status](/assets/images/help/profile/set-status-button.png) + ![Screenshot of the Octocat profile page emphasizing the location, local time, and relative time fields.](/assets/images/help/profile/profile-relative-time.png) + +{% data reusables.user-settings.access_settings %} +1. Under **Location**, type the location you want to be displayed on your profile. + + ![Screenshot of the location and local time settings emphasizing the location field.](/assets/images/help/profile/location-field.png) + +1. Optionally, to display the current local time on your profile, select **Display current local time**. + + ![Screenshot of the location and local time settings emphasizing the display current local time checkbox.](/assets/images/help/profile/display-local-time-checkbox.png) + + - Select the **Time zone** dropdown menu, then click your local time zone. + + ![Screenshot of the location and local time settings emphasizing the time zone dropdown menu.](/assets/images/help/profile/time-zone-dropdown.png) + +{% data reusables.profile.update-profile %} + +{% endif %} + +## Setting a status + +You can set a status to display information about your current availability on {% data variables.product.product_name %}. Your status will show: +- on your {% data variables.product.product_name %} profile page. +- when people hover over your username or avatar on {% data variables.product.product_name %}. +- on a team page for a team where you're a team member. For more information, see "[About teams](/articles/about-teams/#team-pages)." +- on the organization dashboard in an organization where you're a member. For more information, see "[About your organization dashboard](/articles/about-your-organization-dashboard/)." + +When you set your status, you can also let people know that you have limited availability on {% data variables.product.product_name %}. + +![At-mentioned username shows "busy" note next to username](/assets/images/help/profile/username-with-limited-availability-text.png) + +![Requested reviewer shows "busy" note next to username](/assets/images/help/profile/request-a-review-limited-availability-status.png) + +If you select the "Busy" option, when people @mention your username, assign you an issue or pull request, or request a pull request review from you, a note next to your username will show that you're busy. You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." + +1. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Set your status** or, if you already have a status set, click your current status. + ![Button on profile to set your status](/assets/images/help/profile/set-status-on-profile.png) +2. To add custom text to your status, click in the text field and type a status message. + ![Field to type a status message](/assets/images/help/profile/type-a-status-message.png) +3. Optionally, to set an emoji status, click the smiley icon and select an emoji from the list. + ![Button to select an emoji status](/assets/images/help/profile/select-emoji-status.png) +4. Optionally, if you'd like to share that you have limited availability, select "Busy." + ![Busy option selected in Edit status options](/assets/images/help/profile/limited-availability-status.png) +5. Use the **Clear status** drop-down menu, and select when you want your status to expire. If you don't select a status expiration, you will keep your status until you clear or edit your status. + ![Drop down menu to choose when your status expires](/assets/images/help/profile/status-expiration.png) +6. Use the drop-down menu and click the organization you want your status visible to. If you don't select an organization, your status will be public. + ![Drop down menu to choose who your status is visible to](/assets/images/help/profile/status-visibility.png) +7. Click **Set status**. + ![Button to set status](/assets/images/help/profile/set-status-button.png) {% ifversion fpt or ghec %} -## Exibir selos no seu perfil +## Displaying badges on your profile -Ao participar de determinados programas, {% data variables.product.prodname_dotcom %} exibe automaticamente um selo no seu perfil. +When you participate in certain programs, {% data variables.product.prodname_dotcom %} automatically displays a badge on your profile. -| Selo | Programa | Descrição | +| Badge | Program | Description | | --- | --- | --- | -| {% octicon "cpu" aria-label="The Developer Program icon" %} | **Membro do programa de desenvolvedores** | Se você for um integrante registrado do Programa de Desenvolvedor de {% data variables.product.prodname_dotcom %}, ao criar um aplicativo com a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, você receberá um selo de integrante do Programa no seu perfil. Para obter mais informações sobre o Programa de Desenvolvedores do {% data variables.product.prodname_dotcom %}, confira [GitHub Developer](/program/). | -| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | Se você usar {% data variables.product.prodname_pro %}, você receberá um selo PRO no seu perfil. Para obter mais informações sobre o {% data variables.product.prodname_pro %}, confira "[Produtos do {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products#github-pro)". | -| {% octicon "lock" aria-label="The lock icon" %} | **Security Bug Bounty Hunter** | Se você ajudou a identificar vulnerabilidades de segurança, o seu perfil receberá um selo Security Bug Bounty Hunter. Para obter mais informações sobre os dados Programa de segurança do {% data variables.product.prodname_dotcom %}, confira [Segurança do {% data variables.product.prodname_dotcom %}](https://bounty.github.com/). | -| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **Campus Expert do {% data variables.product.prodname_dotcom %}** | Se você participar do {% data variables.product.prodname_campus_program %}, você receberá um selo do especialista de campus de {% data variables.product.prodname_dotcom %} no seu perfil. Para obter mais informações sobre o programa Campus Experts, confira [Campus Experts](https://education.github.com/experts). | -| {% octicon "shield" aria-label="The shield icon" %} | **Crédito de aviso de segurança** | Se um aviso de segurança que você enviar ao [{% data variables.product.prodname_dotcom %} Advisory Database](https://github.com/advisories) for aceito, você receberá um selo de crédito de aviso de segurança em seu perfil. Para obter mais informações sobre avisos de segurança do {% data variables.product.prodname_dotcom %}, confira [Avisos de segurança do {% data variables.product.prodname_dotcom %}](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories). | -| {% octicon "check" aria-label="The check icon" %} | **Discussão respondida** | Se sua resposta a uma discussão for marcada como a resposta, você receberá um selo de discussão respondida em seu perfil. Para obter mais informações sobre as Discussões do {% data variables.product.prodname_dotcom %}, confira [Sobre as discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions). | +| {% octicon "cpu" aria-label="The Developer Program icon" %} | **Developer Program Member** | If you're a registered member of the {% data variables.product.prodname_dotcom %} Developer Program, building an app with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, you'll get a Developer Program Member badge on your profile. For more information on the {% data variables.product.prodname_dotcom %} Developer Program, see [GitHub Developer](/program/). | +| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | If you use {% data variables.product.prodname_pro %} you'll get a PRO badge on your profile. For more information about {% data variables.product.prodname_pro %}, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products#github-pro)." | +| {% octicon "lock" aria-label="The lock icon" %} | **Security Bug Bounty Hunter** | If you helped out hunting down security vulnerabilities, you'll get a Security Bug Bounty Hunter badge on your profile. For more information about the {% data variables.product.prodname_dotcom %} Security program, see [{% data variables.product.prodname_dotcom %} Security](https://bounty.github.com/). | +| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **{% data variables.product.prodname_dotcom %} Campus Expert** | If you participate in the {% data variables.product.prodname_campus_program %}, you will get a {% data variables.product.prodname_dotcom %} Campus Expert badge on your profile. For more information about the Campus Experts program, see [Campus Experts](https://education.github.com/experts). | +| {% octicon "shield" aria-label="The shield icon" %} | **Security advisory credit** | If a security advisory you submit to the [{% data variables.product.prodname_dotcom %} Advisory Database](https://github.com/advisories) is accepted, you'll get a Security advisory credit badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Security Advisories, see [{% data variables.product.prodname_dotcom %} Security Advisories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories). | +| {% octicon "check" aria-label="The check icon" %} | **Discussion answered** | If your reply to a discussion is marked as the answer, you'll get a Discussion answered badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Discussions, see [About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions). | {% endif %} {% ifversion fpt or ghec %} -## Conquistas de ganho +## Earning Achievements -As conquistas celebram eventos e ações específicos que ocorrem no {% data variables.product.prodname_dotcom %}. Eles aparecerão como pequenos selos listados na barra lateral do perfil. Ao clicar ou passar o mouse em uma conquista, você verá uma exibição detalhada indicando como a conquista foi obtida, com uma breve descrição e links para os eventos contribuintes. Os links de evento só ficarão visíveis para os usuários com acesso ao repositório ou à organização em que o evento ocorreu. Os links de evento aparecerão inacessíveis a todos os usuários sem acesso. +Achievements celebrate specific events and actions that happen on {% data variables.product.prodname_dotcom %}. They will appear as small badges listed in the sidebar of your profile. Clicking or hovering on an achievement will show a detailed view that hints at how the achievement was earned, with a short description and links to the contributing events. The event links will only be visible to users that have access to the repository or organization that the event took place in. Event links will appear inaccessible to all users without access. -Para impedir que as contribuições privadas sejam contabilizadas nas suas Conquistas ou para desativar totalmente as Conquistas, confira "[Como mostrar as contribuições privadas e conquistas em seu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)". +To stop private contributions from counting toward your Achievements, or to turn off Achievements entirely, see "[Showing your private contributions and Achievements on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)." {% note %} -**Observação**: no momento, esse recurso está em versão beta e sujeito a alterações. +**Note:** This feature is currently in beta and subject to change. {% endnote %} {% endif %} -## Lista de repositórios qualificados para o selo de Colaborador no Helicóptero de Marte de 2020 +## List of qualifying repositories for Mars 2020 Helicopter Contributor achievement -Se você criou algum commit presente no histórico de commit da tag listada em um ou mais dos repositórios abaixo, receberá o selo de Colaborador no Helicóptero de Marte de 2020 em seu perfil. O commit da autoria tem que estar com um endereço de e-mail verificado associado à sua conta no momento em que {% data variables.product.prodname_dotcom %} determinou as contribuições elegíveis, para ser atribuído a você. Você pode ser o autor original ou [um dos coautores](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) do commit. As alterações futuras em e-mails verificados não terão efeito no selo. Criamos a lista com base nas informações recebidas do Laboratório de Propulsão de Jato da NASA. +If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor achievement on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. You can be the original author or [one of the co-authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) of the commit. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory. -| {% data variables.product.prodname_dotcom %} Repositório | Versão | Marca | +| {% data variables.product.prodname_dotcom %} Repository | Version | Tag | |---|---|---| | [torvalds/linux](https://github.com/torvalds/linux) | 3.4 | [v3.4](https://github.com/torvalds/linux/releases/tag/v3.4) | | [python/cpython](https://github.com/python/cpython) | 3.9.2 | [v3.9.2](https://github.com/python/cpython/releases/tag/v3.9.2) | @@ -178,7 +208,7 @@ Se você criou algum commit presente no histórico de commit da tag listada em u | [matplotlib/cycler](https://github.com/matplotlib/cycler) | 0.10.0 | [v0.10.0](https://github.com/matplotlib/cycler/releases/tag/v0.10.0) | | [elastic/elasticsearch-py](https://github.com/elastic/elasticsearch-py) | 6.8.1 | [6.8.1](https://github.com/elastic/elasticsearch-py/releases/tag/6.8.1) | | [ianare/exif-py](https://github.com/ianare/exif-py) | 2.3.2 | [2.3.2](https://github.com/ianare/exif-py/releases/tag/2.3.2) | -| [kjd/idna](https://github.com/kjd/idna) | 2,10 | [v2.10](https://github.com/kjd/idna/releases/tag/v2.10) | +| [kjd/idna](https://github.com/kjd/idna) | 2.10 | [v2.10](https://github.com/kjd/idna/releases/tag/v2.10) | | [jmespath/jmespath.py](https://github.com/jmespath/jmespath.py) | 0.10.0 | [0.10.0](https://github.com/jmespath/jmespath.py/releases/tag/0.10.0) | | [nucleic/kiwi](https://github.com/nucleic/kiwi) | 1.3.1 | [1.3.1](https://github.com/nucleic/kiwi/releases/tag/1.3.1) | | [matplotlib/matplotlib](https://github.com/matplotlib/matplotlib) | 3.3.4 | [v3.3.4](https://github.com/matplotlib/matplotlib/releases/tag/v3.3.4) | @@ -187,7 +217,7 @@ Se você criou algum commit presente no histórico de commit da tag listada em u | [python-pillow/Pillow](https://github.com/python-pillow/Pillow) | 8.1.0 | [8.1.0](https://github.com/python-pillow/Pillow/releases/tag/8.1.0) | | [pycurl/pycurl](https://github.com/pycurl/pycurl) | 7.43.0.6 | [REL_7_43_0_6](https://github.com/pycurl/pycurl/releases/tag/REL_7_43_0_6) | | [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing) | 2.4.7 | [pyparsing_2.4.7](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.7) | -| [pyserial/pyserial](https://github.com/pyserial/pyserial) | 3,5 | [v3.5](https://github.com/pyserial/pyserial/releases/tag/v3.5) | +| [pyserial/pyserial](https://github.com/pyserial/pyserial) | 3.5 | [v3.5](https://github.com/pyserial/pyserial/releases/tag/v3.5) | | [dateutil/dateutil](https://github.com/dateutil/dateutil) | 2.8.1 | [2.8.1](https://github.com/dateutil/dateutil/releases/tag/2.8.1) | | [yaml/pyyaml ](https://github.com/yaml/pyyaml) | 5.4.1 | [5.4.1](https://github.com/yaml/pyyaml/releases/tag/5.4.1) | | [psf/requests](https://github.com/psf/requests) | 2.25.1 | [v2.25.1](https://github.com/psf/requests/releases/tag/v2.25.1) | @@ -234,10 +264,10 @@ Se você criou algum commit presente no histórico de commit da tag listada em u | [JodaOrg/joda-time](https://github.com/JodaOrg/joda-time) | 2.10.1 | [v2.10.1](https://github.com/JodaOrg/joda-time/releases/tag/v2.10.1) | | [tdunning/t-digest](https://github.com/tdunning/t-digest) | 3.2 | [t-digest-3.2](https://github.com/tdunning/t-digest/releases/tag/t-digest-3.2) | | [HdrHistogram/HdrHistogram](https://github.com/HdrHistogram/HdrHistogram) | 2.1.9 | [HdrHistogram-2.1.9](https://github.com/HdrHistogram/HdrHistogram/releases/tag/HdrHistogram-2.1.9) | -| [locationtech/spatial4j](https://github.com/locationtech/spatial4j) | 0,7 | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7) | +| [locationtech/spatial4j](https://github.com/locationtech/spatial4j) | 0.7 | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7) | | [locationtech/jts](https://github.com/locationtech/jts) | 1.15.0 | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0) | -| [apache/logging-log4j2](https://github.com/apache/logging-log4j2) | 2,11 | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0) | +| [apache/logging-log4j2](https://github.com/apache/logging-log4j2) | 2.11 | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0) | -## Leitura adicional +## Further reading -- "[Sobre seu perfil](/articles/about-your-profile)" +- "[About your profile](/articles/about-your-profile)" diff --git a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md index c39ef22235..9b7fb1a826 100644 --- a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md @@ -275,7 +275,7 @@ This list describes the recommended approaches for accessing repository data wit {% ifversion fpt or ghec %}**Self-hosted**{% elsif ghes or ghae %}Self-hosted{% endif %} runners for {% data variables.product.product_name %} do not have guarantees around running in ephemeral clean virtual machines, and can be persistently compromised by untrusted code in a workflow. -{% ifversion fpt or ghec %}As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal repositories, as anyone who can fork the repository and open a pull request (generally those with read access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the `GITHUB_TOKEN` which, depending on its settings, can grant write access to the repository. Although workflows can control access to environment secrets by using environments and required reviews, these workflows are not run in an isolated environment and are still susceptible to the same risks when run on a self-hosted runner. +{% ifversion fpt or ghec %}As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal repositories, as anyone who can fork the repository and open a pull request (generally those with read access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the `GITHUB_TOKEN` which, depending on its settings, can grant write access to the repository. Although workflows can control access to environment secrets by using environments and required reviews, these workflows are not run in an isolated environment and are still susceptible to the same risks when run on a self-hosted runner. When a self-hosted runner is defined at the organization or enterprise level, {% data variables.product.product_name %} can schedule workflows from multiple repositories onto the same runner. Consequently, a security compromise of these environments can result in a wide impact. To help reduce the scope of a compromise, you can create boundaries by organizing your self-hosted runners into separate groups. You can restrict what {% ifversion restrict-groups-to-workflows %}workflows, {% endif %}organizations and repositories can access runner groups. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)." diff --git a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md index ff0ad40eff..bd71918b12 100644 --- a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md +++ b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md @@ -1,7 +1,7 @@ --- -title: Fazer backup e restaurar o GitHub Enterprise Server com o GitHub Actions habilitado +title: Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled shortTitle: Backing up and restoring -intro: 'Os dados de {% data variables.product.prodname_actions %} no seu provedor de armazenamento externo não estão incluídos em backups regulares de {% data variables.product.prodname_ghe_server %} e precisam ser salvos separadamente.' +intro: 'To restore a backup of {% data variables.product.product_location %} when {% data variables.product.prodname_actions %} is enabled, you must configure {% data variables.product.prodname_actions %} before restoring the backup with {% data variables.product.prodname_enterprise_backup_utilities %}.' versions: ghes: '*' type: how_to @@ -12,50 +12,33 @@ topics: - Infrastructure redirect_from: - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled -ms.openlocfilehash: def12b4e9e93a75ee1aa58f8290ca1b6e7d13cd5 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145095914' --- -{% data reusables.actions.enterprise-storage-ha-backups %} -Se você usar {% data variables.product.prodname_enterprise_backup_utilities %} para fazer backup de {% data variables.product.product_location %}, é importante observar que os dados de {% data variables.product.prodname_actions %} armazenados no seu provedor de armazenamento externo não serão incluídos no backup. +## About backups of {% data variables.product.product_name %} when using {% data variables.product.prodname_actions %} -Esta é uma visão geral das etapas necessárias para restaurar {% data variables.product.product_location %} com {% data variables.product.prodname_actions %} para um novo dispositivo: +You can use {% data variables.product.prodname_enterprise_backup_utilities %} to back up and restore the data and configuration for {% data variables.product.product_location %} to a new instance. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)." -1. Confirme se o dispositivo original está off-line. -1. Defina manualmente as configurações de rede no dispositivo de {% data variables.product.prodname_ghe_server %}. As configurações de rede são excluídas do instantâneo de backup e não são substituídas por `ghe-restore`. -1. Para configurar o dispositivo substituto para usar a mesma configuração de armazenamento externo do {% data variables.product.prodname_actions %} do dispositivo original, no novo dispositivo, defina os parâmetros obrigatórios com o comando `ghe-config`. - - - Armazenamento do Blobs do Azure - ```shell - ghe-config secrets.actions.storage.blob-provider "azure" - ghe-config secrets.actions.storage.azure.connection-string "_Connection_String_" - ``` - - Amazon S3 - ```shell - ghe-config secrets.actions.storage.blob-provider "s3" - ghe-config secrets.actions.storage.s3.bucket-name "_S3_Bucket_Name" - ghe-config secrets.actions.storage.s3.service-url "_S3_Service_URL_" - ghe-config secrets.actions.storage.s3.access-key-id "_S3_Access_Key_ID_" - ghe-config secrets.actions.storage.s3.access-secret "_S3_Access_Secret_" - ``` - - Opcionalmente, para habilitar o estilo de caminho S3, digite o comando a seguir: - ```shell - ghe-config secrets.actions.storage.s3.force-path-style true - ``` - +However, not all the data for {% data variables.product.prodname_actions %} is included in these backups. {% data reusables.actions.enterprise-storage-ha-backups %} -1. Habilite {% data variables.product.prodname_actions %} no dispositivo de substituição. Isto conectará o dispositivo de substituição ao mesmo armazenamento externo para {% data variables.product.prodname_actions %}. +## Restoring a backup of {% data variables.product.product_name %} when {% data variables.product.prodname_actions %} is enabled - ```shell - ghe-config app.actions.enabled true - ghe-config-apply - ``` +To restore a backup of {% data variables.product.product_location %} with {% data variables.product.prodname_actions %}, you must manually configure network settings and external storage on the destination instance before you restore your backup from {% data variables.product.prodname_enterprise_backup_utilities %}. -1. Depois que o {% data variables.product.prodname_actions %} estiver configurado e habilitado, use o comando `ghe-restore` para restaurar o restante dos dados do backup. Para obter mais informações, confira "[Como restaurar um backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)". -1. Registre novamente seus executores auto-hospedados no dispositivo de substituição. Para obter mais informações, confira "[Como adicionar executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". +1. Confirm that the source instance is offline. +1. Manually configure network settings on the replacement {% data variables.product.prodname_ghe_server %} instance. Network settings are excluded from the backup snapshot, and are not overwritten by `ghe-restore`. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)." +1. SSH into the destination instance. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." -Para obter mais informações sobre backup e restauração do {% data variables.product.prodname_ghe_server %}, confira "[Como configurar backups no seu dispositivo](/admin/configuration/configuring-backups-on-your-appliance)". + ```shell{:copy} + $ ssh -p 122 admin@HOSTNAME + ``` +1. Configure the destination instance to use the same external storage service for {% data variables.product.prodname_actions %} as the source instance by entering one of the following commands. +{% indented_data_reference reusables.actions.configure-storage-provider-platform-commands spaces=3 %} +{% data reusables.actions.configure-storage-provider %} +1. To prepare to enable {% data variables.product.prodname_actions %} on the destination instance, enter the following command. + + ```shell{:copy} + ghe-config app.actions.enabled true + ``` +{% data reusables.actions.apply-configuration-and-enable %} +1. After {% data variables.product.prodname_actions %} is configured and enabled, to restore the rest of the data from the backup, use the `ghe-restore` command. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)." +1. Re-register your self-hosted runners on the destination instance. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md index 142cbc3a24..6fa069a0f2 100644 --- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md +++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md @@ -1,53 +1,157 @@ --- -title: Configurar uma instância de preparo -intro: 'Você pode configurar uma instância do {% data variables.product.product_name %} em um ambiente separado e isolado e usá-la para validar e testar alterações.' +title: Setting up a staging instance +intro: 'You can set up a {% data variables.product.product_name %} instance in a separate, isolated environment, and use the instance to validate and test changes.' redirect_from: - /enterprise/admin/installation/setting-up-a-staging-instance - /admin/installation/setting-up-a-staging-instance versions: - ghes: '*' + ghes: "*" type: how_to topics: - Enterprise - Infrastructure - Upgrades shortTitle: Set up a staging instance -ms.openlocfilehash: 86006b3dd1fcdd7a7139f35934cafce1f208c8bb -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147065359' +miniTocMaxHeadingLevel: 3 --- -## Sobre instâncias de preparo -O {% data variables.product.company_short %} recomenda que você configure um ambiente separado para testar backups, atualizações ou alterações na configuração do {% data variables.product.product_location %}. Esse ambiente, que você deve isolar de seus sistemas de produção, é chamado de ambiente de preparo. +## About staging instances -Por exemplo, para proteger contra perda de dados, você pode validar regularmente o backup da sua instância de produção. Você pode restaurar regularmente o backup de seus dados de produção em uma instância separada do {% data variables.product.product_name %} em um ambiente de preparo. Nesta instância de preparo, você também pode testar a atualização para a versão mais recente do recurso do {% data variables.product.product_name %}. +{% data variables.product.company_short %} recommends that you set up a separate environment to test backups, updates, or changes to the configuration for {% data variables.product.product_location %}. This environment, which you should isolate from your production systems, is called a staging environment. + +For example, to protect against loss of data, you can regularly validate the backup of your production instance. You can regularly restore the backup of your production data to a separate {% data variables.product.product_name %} instance in a staging environment. On this staging instance, you could also test the upgrade to the latest feature release of {% data variables.product.product_name %}. {% tip %} -**Dica:** talvez seja interessante reutilizar seu arquivo de licença do {% data variables.product.prodname_enterprise %}, desde que a instância de preparo não seja usada em uma capacidade de produção. +**Tip:** You may reuse your existing {% data variables.product.prodname_enterprise %} license file as long as the staging instance is not used in a production capacity. {% endtip %} -## Considerações sobre um ambiente de preparo +## Considerations for a staging environment -Para testar minuciosamente o {% data variables.product.product_name %} e recriar um ambiente com a maior semelhança possível com o ambiente de produção, considere os sistemas externos que interagem com sua instância. Por exemplo, faça os testes a seguir em seu ambiente de preparo. +To thoroughly test {% data variables.product.product_name %} and recreate an environment that's as similar to your production environment as possible, consider the external systems that interact with your instance. For example, you may want to test the following in your staging environment. -- Autenticação, principalmente se você usa um provedor de autenticação externo, como o SAML -- Integração com um sistema externo de geração de tíquetes; -- Integração com um servidor de integração contínua; -- Software ou scripts externos que usam a {% data variables.product.prodname_enterprise_api %}; -- Servidor externo SMTP para notificações de e-mail. +- Authentication, especially if you use an external authentication provider like SAML +- Integration with an external ticketing system +- Integration with a continuous integration server +- External scripts or software that use the {% data variables.product.prodname_enterprise_api %} +- External SMTP server for email notifications -## Configurar uma instância de preparo +## Setting up a staging instance -1. Faça backup da sua instância de produção usando o {% data variables.product.prodname_enterprise_backup_utilities %}. Para obter mais informações, confira a seção "Sobre dados de {% data variables.product.prodname_enterprise_backup_utilities %}" em "[Como configurar backups em seu dispositivo](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#about-github-enterprise-server-backup-utilities)". -2. Configure uma nova instância para funcionar como ambiente de preparo. Você pode usar os mesmos guias para provisionar e instalar sua instância de preparo, assim como fez na instância de produção. Para obter mais informações, confira "[Como configurar uma instância do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)". -3. Opcionalmente, se você planeja testar a funcionalidade do {% data variables.product.prodname_actions %} em seu ambiente de teste, examine as considerações sobre seus logs e seu armazenamento. Para obter mais informações, veja "[Como usar um ambiente de preparo](/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment)". -4. Restaure o backup na sua instância de preparo. Para obter mais informações, confira a seção "Como restaurar um backup" de "[Como configurar backups em seu dispositivo](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#restoring-a-backup)". +You can set up a staging instance from scratch and configure the instance however you like. For more information, see "[Setting up a {% data variables.product.product_name %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)" and "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)." -## Leitura adicional +Alternatively, you can create a staging instance that reflects your production configuration by restoring a backup of your production instance to the staging instance. -- "[Sobre atualizações em novas versões](/admin/overview/about-upgrades-to-new-releases)" +1. [Back up your production instance](#1-back-up-your-production-instance). +2. [Set up a staging instance](#2-set-up-a-staging-instance). +3. [Configure {% data variables.product.prodname_actions %}](#3-configure-github-actions). +4. [Configure {% data variables.product.prodname_registry %}](#4-configure-github-packages). +5. [Restore your production backup](#5-restore-your-production-backup). +6. [Review the instance's configuration](#6-review-the-instances-configuration). +7. [Apply the instance's configuration](#7-apply-the-instances-configuration). + +### 1. Back up your production instance + +If you want to test changes on an instance that contains the same data and configuration as your production instance, back up the data and configuration from the production instance using {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)." + +{% warning %} + +**Warning**: If you use {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} in production, your backup will include your production configuration for external storage. To avoid potential loss of data by writing to your production storage from your staging instance, you must configure each feature in steps 3 and 4 before you restore your backup. + +{% endwarning %} + +### 2. Set up a staging instance + +Set up a new instance to act as your staging environment. You can use the same guides for provisioning and installing your staging instance as you did for your production instance. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)." + +If you plan to restore a backup of your production instance, continue to the next step. Alternatively, you can configure the instance manually and skip the following steps. + +### 3. Configure {% data variables.product.prodname_actions %} + +Optionally, if you use {% data variables.product.prodname_actions %} on your production instance, configure the feature on the staging instance before restoring your production backup. If you don't use {% data variables.product.prodname_actions %}, skip to "[4. Configure {% data variables.product.prodname_registry %}](#4-configure-github-packages)." + +{% warning %} + +**Warning**: If you don't configure {% data variables.product.prodname_actions %} on the staging instance before restoring your production backup, your staging instance will use your production instance's external storage, which could result in loss of data. We strongly recommended that you use different external storage for your staging instance. For more information, see "[Using a staging environment](/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment)." + +{% endwarning %} + +{% data reusables.enterprise_installation.ssh-into-staging-instance %} +1. To configure the staging instance to use an external storage provider for {% data variables.product.prodname_actions %}, enter one of the following commands. +{% indented_data_reference reusables.actions.configure-storage-provider-platform-commands spaces=3 %} +{% data reusables.actions.configure-storage-provider %} +1. To prepare to enable {% data variables.product.prodname_actions %} on the staging instance, enter the following command. + + ```shell{:copy} + ghe-config app.actions.enabled true + ``` + +### 4. Configure {% data variables.product.prodname_registry %} + +Optionally, if you use {% data variables.product.prodname_registry %} on your production instance, configure the feature on the staging instance before restoring your production backup. If you don't use {% data variables.product.prodname_registry %}, skip to "[5. Restore your production backup](#5-restore-your-production-backup)." + +{% warning %} + +**Warning**: If you don't configure {% data variables.product.prodname_actions %} on the staging instance before restoring your production backup, your staging instance will use your production instance's external storage, which could result in loss of data. We strongly recommended that you use different external storage for your staging instance. + +{% endwarning %} + +1. Review the backup you will restore to the staging instance. + - If you took the backup with {% data variables.product.prodname_enterprise_backup_utilities %} 3.5 or later, the backup includes the configuration for {% data variables.product.prodname_registry %}. Continue to the next step. + - If you took the backup with {% data variables.product.prodname_enterprise_backup_utilities %} 3.4 or earlier, configure {% data variables.product.prodname_registry %} on the staging instance. For more information, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." +{% data reusables.enterprise_installation.ssh-into-staging-instance %} +1. Configure the external storage connection by entering the following commands, replacing the placeholder values with actual values for your connection. + - Azure Blob Storage: + + ```shell{:copy} + ghe-config secrets.packages.blob-storage-type "azure" + ghe-config secrets.packages.azure-container-name "AZURE CONTAINER NAME" + ghe-config secrets.packages.azure-connection-string "CONNECTION STRING" + ``` + - Amazon S3: + + ```shell{:copy} + ghe-config secrets.packages.blob-storage-type "s3" + ghe-config secrets.packages.service-url "S3 SERVICE URL" + ghe-config secrets.packages.s3-bucket "S3 BUCKET NAME" + ghe-config secrets.packages.aws-access-key "S3 ACCESS KEY ID" + ghe-config secrets.packages.aws-secret-key "S3 ACCESS SECRET" + ``` +1. To prepare to enable {% data variables.product.prodname_registry %} on the staging instance, enter the following command. + + ```shell{:copy} + ghe-config app.packages.enabled true + ``` + +### 5. Restore your production backup + +Use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)." + +If the staging instance is already configured and you're about to overwrite settings, certificate, and license data, add the `-c` option to the command. For more information about the option, see [Using the backup and restore commands](https://github.com/github/backup-utils/blob/master/docs/usage.md#restoring-settings-tls-certificate-and-license) in the {% data variables.product.prodname_enterprise_backup_utilities %} documentation. + +### 6. Review the instance's configuration + +To access the staging instance using the same hostname, update your local hosts file to resolve the staging instance's hostname by IP address by editing the `/etc/hosts` file in macOS or Linux, or the `C:\Windows\system32\drivers\etc` file in Windows. + +{% note %} + +**Note**: Your staging instance must be accessible from the same hostname as your production instance. Changing the hostname for {% data variables.product.product_location %} is not supported. For more information, see "[Configuring a hostname](/admin/configuration/configuring-network-settings/configuring-a-hostname)." + +{% endnote %} + +Then, review the staging instance's configuration in the {% data variables.enterprise.management_console %}. For more information, see "[Accessing the {% data variables.enterprise.management_console %}](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)." + +{% warning %} + +**Warning**: If you configured {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} for the staging instance, to avoid overwriting production data, ensure that the external storage configuration in the {% data variables.enterprise.management_console %} does not match your production instance. + +{% endwarning %} + +### 7. Apply the instance's configuration + +To apply the configuration from the {% data variables.enterprise.management_console %}, click **Save settings**. + +## Further reading + +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" diff --git a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md index f0ef5e37da..63db7352b5 100644 --- a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md +++ b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md @@ -150,7 +150,7 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | Keyboard shortcut | Description |-----------|------------ -|⌘+f (Mac) or Ctrl+f (Windows/Linux) | Focus filter field +|Command+f (Mac) or Ctrl+f (Windows/Linux) | Focus filter field |← | Move cell focus to the left |→ | Move cell focus to the right |↑ | Move cell focus up @@ -162,7 +162,7 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |-----------|------------ |Enter | Toggle edit mode for the focused cell |Escape | Cancel editing for the focused cell -|⌘+Shift+\ (Mac) or Ctrl+Shift+\ (Windows/Linux) | Open row actions menu +|Command+Shift+\ (Mac) or Ctrl+Shift+\ (Windows/Linux) | Open row actions menu |Shift+Space | Select item |Space | Open selected item |e | Archive selected items diff --git a/translations/pt-BR/content/index.md b/translations/pt-BR/content/index.md index b3e5601692..d4e5d5db26 100644 --- a/translations/pt-BR/content/index.md +++ b/translations/pt-BR/content/index.md @@ -75,6 +75,10 @@ childGroups: octicon: ShieldLockIcon children: - code-security + - code-security/supply-chain-security + - code-security/dependabot + - code-security/code-scanning + - code-security/secret-scanning - name: Client apps octicon: DeviceMobileIcon children: diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md index 232135b92a..58f47d8e9d 100644 --- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md @@ -1,6 +1,6 @@ --- -title: Gerenciando as configurações de segurança e de análise da sua organização -intro: 'Você pode controlar recursos que protegem e analisam o código nos projetos da sua organização no {% data variables.product.prodname_dotcom %}.' +title: Managing security and analysis settings for your organization +intro: 'You can control features that secure and analyze the code in your organization''s projects on {% data variables.product.prodname_dotcom %}.' permissions: Organization owners can manage security and analysis settings for repositories in the organization. redirect_from: - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization @@ -15,115 +15,156 @@ topics: - Organizations - Teams shortTitle: Manage security & analysis -ms.openlocfilehash: 83104f606266279a239c5173e838c9241832fb84 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147063207' --- -## Sobre a gestão de configurações de segurança e análise -O {% data variables.product.prodname_dotcom %} pode ajudar a proteger os repositórios na sua organização. É possível gerenciar os recursos de segurança e análise para todos os repositórios existentes ou novos que os integrantes criarem na sua organização. {% ifversion ghec %}Se você tiver uma licença para {% data variables.product.prodname_GH_advanced_security %}, você também poderá gerenciar o acesso a essas funcionalidades. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}Organizações que usam {% data variables.product.prodname_ghe_cloud %} com uma licença para {% data variables.product.prodname_GH_advanced_security %} também podem gerenciar o acesso a essas funcionalidades. Para obter mais informações, confira a [documentação do {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).{% endif %} +## About management of security and analysis settings -{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} {% data reusables.security.security-and-analysis-features-enable-read-only %} +{% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. {% ifversion ghec %}If you have a license for {% data variables.product.prodname_GH_advanced_security %} then you can also manage access to these features. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can also manage access to these features. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).{% endif %} -## Exibir as configurações de segurança e análise +{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +{% data reusables.security.security-and-analysis-features-enable-read-only %} -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security-and-analysis %} +## Displaying the security and analysis settings -A página exibida permite que você habilite ou desabilite todas as funcionalidades de segurança e análise dos repositórios na sua organização. +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.organizations.security-and-analysis %} -{% ifversion ghec %}Se a sua organização pertence a uma empresa com uma licença para {% data variables.product.prodname_GH_advanced_security %}, a página também conterá opções para habilitar e desabilitar funcionalidades do {% data variables.product.prodname_advanced_security %}. Todos os repositórios que usam {% data variables.product.prodname_GH_advanced_security %} estão listados na parte inferior da página.{% endif %} +The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. -{% ifversion ghes %}Se você tiver uma licença para {% data variables.product.prodname_GH_advanced_security %}, a página também conterá opções para habilitar e desabilitar funcionalidades do {% data variables.product.prodname_advanced_security %}. Todos os repositórios que usam {% data variables.product.prodname_GH_advanced_security %} estão listados na parte inferior da página.{% endif %} +{% ifversion ghec %}If your organization belongs to an enterprise with a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %} -{% ifversion ghae %}A página também conterá opções para habilitar e desabilitar funcionalidades do {% data variables.product.prodname_advanced_security %}. Todos os repositórios que usam {% data variables.product.prodname_GH_advanced_security %} estão listados na parte inferior da página.{% endif %} +{% ifversion ghes %}If you have a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %} -## Como habilitar ou desabilitar um recurso para todos os repositórios existentes +{% ifversion ghae %}The page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %} -Você pode habilitar ou desabilitar funcionalidades para todos os repositórios. {% ifversion fpt or ghec %}O impacto de suas alterações nos repositórios da organização é determinado pela visibilidade: +## Enabling or disabling a feature for all existing repositories -- **Grafo de dependência** – Suas alterações afetam apenas repositórios privados porque a funcionalidade está sempre habilitada para repositórios públicos. -- **{% data variables.product.prodname_dependabot_alerts %}** – Suas alterações afetam todos os repositórios. -- **{% data variables.product.prodname_dependabot_security_updates %}** – Suas alterações afetam todos os repositórios. +You can enable or disable features for all repositories. +{% ifversion fpt or ghec %}The impact of your changes on repositories in your organization is determined by their visibility: + +- **Dependency graph** - Your changes affect only private repositories because the feature is always enabled for public repositories. +- **{% data variables.product.prodname_dependabot_alerts %}** - Your changes affect all repositories. +- **{% data variables.product.prodname_dependabot_security_updates %}** - Your changes affect all repositories. {%- ifversion ghec %} -- **{% data variables.product.prodname_GH_advanced_security %}** – As suas alterações afetam apenas repositórios privados, porque {% data variables.product.prodname_GH_advanced_security %} e as funcionalidades relacionadas estão sempre habilitadas em repositórios públicos. -- **{% data variables.product.prodname_secret_scanning_caps %}** – Suas alterações afetam repositórios em que o {% data variables.product.prodname_GH_advanced_security %} também está habilitado. Esta opção controla se {% data variables.product.prodname_secret_scanning_GHAS %} está habilitado ou não. {% data variables.product.prodname_secret_scanning_partner_caps %} sempre é executado em todos os repositórios públicos. +- **{% data variables.product.prodname_GH_advanced_security %}** - Your changes affect only private repositories because {% data variables.product.prodname_GH_advanced_security %} and the related features are always enabled for public repositories. +- **{% data variables.product.prodname_secret_scanning_caps %}** - Your changes affect repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. This option controls whether or not {% data variables.product.prodname_secret_scanning_GHAS %} is enabled. {% data variables.product.prodname_secret_scanning_partner_caps %} always runs on all public repositories. {% endif %} {% endif %} {% data reusables.advanced-security.note-org-enable-uses-seats %} -1. Vá para as configurações de segurança e análise da sua organização. Para obter mais informações, confira "[Como exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)". -2. Em "Segurança e análise de código", à direita do recurso, clique em **Desabilitar tudo** ou **Habilitar tudo**. {% ifversion ghes or ghec %}O controle de "{% data variables.product.prodname_GH_advanced_security %}" será desabilitado se você não tiver estações disponíveis na licença do {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% ifversion fpt %} ![Botão "Habilitar tudo" ou "Desabilitar tudo" dos recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-fpt.png) {% endif %} {% ifversion ghec %} ![Botão "Habilitar tudo" ou "Desabilitar tudo" dos recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-ghec.png) {% endif %} {% ifversion ghes > 3.2 %} ![Botão "Habilitar tudo" ou "Desabilitar tudo" dos recursos de "Configurar segurança e análise"](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png) {% endif %} {% ifversion ghes = 3.2 %} ![Botão "Habilitar tudo" ou "Desabilitar tudo" dos recursos de "Configurar segurança e análise"](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png) {% endif %} +{% ifversion ghes or ghec or ghae %} +{% note %} + +**Note:** If you encounter an error that reads "GitHub Advanced Security cannot be enabled because of a policy setting for the organization," contact your enterprise admin and ask them to change the GitHub Advanced Security policy for your enterprise. For more information, see "[Enforcing policies for Advanced Security in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)." +{% endnote %} +{% endif %} + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +2. Under "Code security and analysis", to the right of the feature, click **Disable all** or **Enable all**. {% ifversion ghes or ghec %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if you have no available seats in your {% data variables.product.prodname_GH_advanced_security %} license.{% endif %} + {% ifversion fpt %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-fpt.png) + {% endif %} + {% ifversion ghec %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-ghec.png) + {% endif %} + {% ifversion ghes > 3.2 %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png) + {% endif %} + {% ifversion ghes = 3.2 %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png) + {% endif %} - {% ifversion ghae %} ![Botão "Habilitar tudo" ou "Desabilitar tudo" para as funcionalidades de "Configurar segurança e análise"](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png) {% endif %} {% ifversion fpt or ghec %} -3. Opcionalmente, habilite o recurso para novos repositórios na organização por padrão. - {% ifversion fpt or ghec %} ![Opção "Habilitar por padrão" para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) {% endif %} + {% ifversion ghae %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png) + {% endif %} + {% ifversion fpt or ghec %} +3. Optionally, enable the feature by default for new repositories in your organization. + {% ifversion fpt or ghec %} + !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) + {% endif %} - {% endif %} {% ifversion fpt or ghec %} -4. Clique em **Desabilitar RECURSO** ou em **Habilitar RECURSO** para habilitar ou desabilitar o recurso em todos os repositórios em sua organização. - {% ifversion fpt or ghec %} ![Botão para desabilitar ou habilitar o recurso](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) {% endif %} + {% endif %} + {% ifversion fpt or ghec %} +4. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. + {% ifversion fpt or ghec %} + ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + {% endif %} - {% endif %} {% ifversion ghae or ghes %} -3. Clique em **Habilitar/Desabilitar tudo** ou **Habilitar/Desabilitar para repositórios qualificados** a fim de confirmar a alteração. - ![Botão para habilitar o recurso para todos os repositórios qualificados na organização](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png) {% endif %} + {% endif %} + {% ifversion ghae or ghes %} +5. Click **Enable/Disable all** or **Enable/Disable for eligible repositories** to confirm the change. + ![Button to enable feature for all the eligible repositories in the organization](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png) + {% endif %} {% data reusables.security.displayed-information %} -## Habilitar ou desabilitar uma funcionalidade automaticamente quando novos repositórios forem adicionados +## Enabling or disabling a feature automatically when new repositories are added -1. Vá para as configurações de segurança e análise da sua organização. Para obter mais informações, confira "[Como exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)". -2. Em "Segurança e análise de código", à direita do revurso, habilite ou desabilite o recurso por padrão para novos repositórios{% ifversion fpt or ghec %}, ou todos os novos repositórios privados,{% endif %} na sua organização. - {% ifversion fpt or ghec %} ![Captura de tela de uma caixa de seleção para habilitar um recurso em novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) {% endif %} {% ifversion ghes > 3.2 %} ![Captura de tela de uma caixa de seleção para habilitar um recurso em novos repositórios](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) {% endif %} {% ifversion ghes = 3.2 %} ![Captura de tela de uma caixa de seleção para habilitar um recurso em novos repositórios](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) {% endif %} {% ifversion ghae %} ![Captura de tela de uma caixa de seleção para habilitar um recurso em novos repositórios](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png) {% endif %} +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +2. Under "Code security and analysis", to the right of the feature, enable or disable the feature by default for new repositories{% ifversion fpt or ghec %}, or all new private repositories,{% endif %} in your organization. + {% ifversion fpt or ghec %} + ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) + {% endif %} + {% ifversion ghes > 3.2 %} + ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) + {% endif %} + {% ifversion ghes = 3.2 %} + ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) + {% endif %} + {% ifversion ghae %} + ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png) + {% endif %} {% ifversion fpt or ghec or ghes > 3.2 %} -## Permitir que {% data variables.product.prodname_dependabot %} acesse dependências privadas +## Allowing {% data variables.product.prodname_dependabot %} to access private dependencies -{% data variables.product.prodname_dependabot %} pode verificar referências de dependências desatualizadas em um projeto e gerar automaticamente um pull request para atualizá-las. Para fazer isso, {% data variables.product.prodname_dependabot %} deve ter acesso a todos os arquivos de dependência de destino. Normalmente, atualizações da versão irão falhar se uma ou mais dependências forem inacessíveis. Para obter mais informações, confira "[Sobre as {% data variables.product.prodname_dependabot %}](/github/administering-a-repository/about-dependabot-version-updates)". +{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to all of the targeted dependency files. Typically, version updates will fail if one or more dependencies are inaccessible. For more information, see "[About {% data variables.product.prodname_dependabot %} version updates](/github/administering-a-repository/about-dependabot-version-updates)." -Por padrão, {% data variables.product.prodname_dependabot %} não pode atualizar as dependências que estão localizadas em repositórios privados ou registros de pacotes privados. Entretanto, se uma dependência estiver em um repositório privado de {% data variables.product.prodname_dotcom %} dentro da mesma organização que o projeto que usa essa dependência, você pode permitir que {% data variables.product.prodname_dependabot %} atualize a versão com sucesso, dando-lhe acesso à hospedagem do repositório. +By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories or private package registries. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. -Se seu código depende de pacotes em um registro privado, você pode permitir que {% data variables.product.prodname_dependabot %} atualize as versões dessas dependências configurando isso no nível do repositório. Você faz isso adicionando detalhes de autenticação ao arquivo _dependabot.yml_ do repositório. Para obter mais informações, confira "[Opções de configuração para o arquivo dependabot.yml](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)". +If your code depends on packages in a private registry, you can allow {% data variables.product.prodname_dependabot %} to update the versions of these dependencies by configuring this at the repository level. You do this by adding authentication details to the _dependabot.yml_ file for the repository. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." -Para permitir que {% data variables.product.prodname_dependabot %} acesse um repositório privado de {% data variables.product.prodname_dotcom %}: +To allow {% data variables.product.prodname_dependabot %} to access a private {% data variables.product.prodname_dotcom %} repository: -1. Vá para as configurações de segurança e análise da sua organização. Para obter mais informações, confira "[Como exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)". -1. Em "Acesso ao repositório privado do {% data variables.product.prodname_dependabot %}", clique em **Adicionar repositórios privados** ou **Adicionar repositórios internos e privados**. - ![Botão para adicionar repositórios](/assets/images/help/organizations/dependabot-private-repository-access.png) -1. Comece a digitar o nome do repositório que deseja permitir. - ![Campo de pesquisa do repositório com menu suspenso filtrado](/assets/images/help/organizations/dependabot-private-repo-choose.png) -1. Clique no repositório que deseja permitir. +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. Under "{% data variables.product.prodname_dependabot %} private repository access", click **Add private repositories** or **Add internal and private repositories**. + ![Add repositories button](/assets/images/help/organizations/dependabot-private-repository-access.png) +1. Start typing the name of the repository you want to allow. + ![Repository search field with filtered dropdown](/assets/images/help/organizations/dependabot-private-repo-choose.png) +1. Click the repository you want to allow. -1. Opcionalmente, para remover um repositório da lista, à direita do repositório, clique em {% octicon "x" aria-label="The X icon" %}. - ![Botão "X" para remover um repositório](/assets/images/help/organizations/dependabot-private-repository-list.png) {% endif %} +1. Optionally, to remove a repository from the list, to the right of the repository, click {% octicon "x" aria-label="The X icon" %}. + !["X" button to remove a repository](/assets/images/help/organizations/dependabot-private-repository-list.png) +{% endif %} {% ifversion ghes or ghec %} -## Remover acesso a {% data variables.product.prodname_GH_advanced_security %} de repositórios individuais em uma organização +## Removing access to {% data variables.product.prodname_GH_advanced_security %} from individual repositories in an organization -Você pode gerenciar o acesso a recursos do {% data variables.product.prodname_GH_advanced_security %} para um repositório na guia "Configurações". Para obter mais informações, confira "[Gerenciando configurações de segurança e análise para seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". No entanto, você também pode desabilitar funcionalidades de {% data variables.product.prodname_GH_advanced_security %} para um repositório na aba "Configurações" da organização. +You can manage access to {% data variables.product.prodname_GH_advanced_security %} features for a repository from its "Settings" tab. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." However, you can also disable {% data variables.product.prodname_GH_advanced_security %} features for a repository from the "Settings" tab for the organization. -1. Vá para as configurações de segurança e análise da sua organização. Para obter mais informações, confira "[Como exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)". -1. Para ver uma lista de todos os repositórios na sua organização com {% data variables.product.prodname_GH_advanced_security %} habilitados, desça até a seção "repositórios de {% data variables.product.prodname_GH_advanced_security %}". - ![Seção de repositórios do {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) A tabela lista o número de committers exclusivos de cada repositório. Este é o número de estações que você poderia liberar em sua licença, removendo acesso a {% data variables.product.prodname_GH_advanced_security %}. Para obter mais informações, confira "[Sobre a cobrança do {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)". -1. Para remover acesso ao {% data variables.product.prodname_GH_advanced_security %} de um repositório e liberar estações usadas por todos os committers que são exclusivos do repositório, clique no {% octicon "x" aria-label="X symbol" %} adjacente. -1. Na caixa de diálogo de confirmação, clique em **Remover repositório** para remover o acesso aos recursos do {% data variables.product.prodname_GH_advanced_security %}. +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. To see a list of all the repositories in your organization with {% data variables.product.prodname_GH_advanced_security %} enabled, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section. + ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) + The table lists the number of unique committers for each repository. This is the number of seats you could free up on your license by removing access to {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)." +1. To remove access to {% data variables.product.prodname_GH_advanced_security %} from a repository and free up seats used by any committers that are unique to the repository, click the adjacent {% octicon "x" aria-label="X symbol" %}. +1. In the confirmation dialog, click **Remove repository** to remove access to the features of {% data variables.product.prodname_GH_advanced_security %}. {% note %} -**Observação:** se você remover o acesso ao {% data variables.product.prodname_GH_advanced_security %} de um repositório, deverá se comunicar com a equipe de desenvolvimento afetada para que eles saibam que a alteração foi intencional. Isso garante que eles não perderão tempo corrigindo execuções falhas de varredura de código. +**Note:** If you remove access to {% data variables.product.prodname_GH_advanced_security %} for a repository, you should communicate with the affected development team so that they know that the change was intended. This ensures that they don't waste time debugging failed runs of code scanning. {% endnote %} {% endif %} -## Leitura adicional +## Further reading -- "[Como proteger seu repositório](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %} -- "[Sobre a verificação de segredos](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %} -- "[Sobre o grafo de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %} -- "[Sobre a segurança da cadeia de fornecedores](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)" +- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %} +- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %} +- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %} +- "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)" diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md index 92900222ad..dff4c98d4d 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md @@ -30,7 +30,7 @@ Prerequisites for repository transfers: - When you transfer a repository that you own to another personal account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %} - To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization. - The target account must not have a repository with the same name, or a fork in the same network. -- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghes < 3.7 %} +- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghes < 3.7 or ghae %} - Internal repositories can't be transferred.{% endif %} - Private forks can't be transferred.